24th July - New Org Pipeline
ICARE
| Environment | Status |
|---|---|
| BugFix (new sandbox) | Ready to be used |
| Weekly Dev 1 (new sandbox) | Ready to be used |
| Weekly Int (new sandbox) | Ready to be used |
| Monthly Int (previously MntProjInt) | Ready to be used |
| Monthly Dev 1 (previously MntDev1) | Ready to be used |
| Monthly Dev 2 (previously MntDev2) | Ready to be used |
| BugFix | Ready to be used |
| Supernova | Ready to be used |
| INT | Ready to be used |
| UAT | Refresh in progress, until next Monday (is not accessible during initial actions) |
Actions for developers to review:
- Developers should create new Copado credentials for the orgs where changes are going to be done (documentation, copado documentation on creating a credential).
- If you have any work in progress that was not deployed to any org before, please reach out for assistance with re-deployment (documentation).
CORE
| Environment | Status |
|---|---|
| BugFix (new sandbox) | Ready to be used |
| Weekly Dev 1 (new sandbox) | Ready to be used |
| WeeklyInt (new sandbox) | Ready to be used |
| MonthlyInt (previously MntProjINT) | Ready to be used |
| MonthlyDev (previously devMonth) | Ready to be used |
| INT | Dataset needs to be confirmed, other actions are completed. It can be accessed and used taking that into account |
| UAT | Refresh in progress, until next Monday (is not accessible during initial actions) |
Actions for developers to review:
- Developers should review the new Gitlab branch conventions and working methods: Gitlab Branching Strategy.
----
If you haven't received the emails to setup your salesforce user for any of these sandboxes, or if you have any sandbox access issue, note it in sandbox refresh troubleshooting document
Others in July
Update Copado Admin / System access
Apex Tests as deployment quality gate
New Release Management procedure
17th July - Updating Credential in User Stories
TL;DR;
As a developer, when considering if it's possible to change a credential in the Copado user story without risk, you just need to check if the credential field is editable:
- If the credential field is editable, you can change it without any risk.
- If the credential field is not editable, changing it poses a risk in terms of affecting back promotions.
Long explanation
As explained in the sessions at the beginning of July, the issue statement is: If a user story has already been deployed to a higher environment (e.g., UAT), and an issue arises, such as a test failure, if we update the credential of the user story back to a dev credential and re-deploy the same user story, the latest changes may not be included in the back promotions.
Through configuration in Copado, as seen in this video https://solvayagile.atlassian.net/browse/CCCME-8318?focusedCommentId=285859, where I explain how it works, the release manager will configure which orgs in the pipeline will allow changes to the credential in the user story. Therefore, the credential fields will be editable to the developer or not:
- If the credential field is editable, you can change it without any risk.
- If the credential field is not editable, changing it poses a risk in terms of affecting back promotions.
June/July - Jira ↔ Copado Enhancements
Fixes:
- Subtasks are synchronized to Copado User stories
- User stories can now have any priority and sync will happen (previously there was a problem with "Major" "Minor" and "Priority 1" among others.
- Sprints and releases are synchronized to copado
- Status is bidirectionally synchronized, and upon deployments to INT, UAT and PROD the status will automatically update in Jira
- Mohan account is no longer used for the integration in Jira, instead a service account is used
- Configure Syensqo.ai project
----------------
In essence, to synchronize any user story / task / bug or subtask, make sure of the following:
Required fields for User Stories, Tasks or Bugs:
- Description
- Assignee
- Priority
- Components = iCARe (and not iCare or iCAre nor ICARE, must be iCARe).
- Sprint
- Fix Version
Required fields for subtasks:
- Fix Version
- Component
Others in May-June
Updated Copado Deployer and Copado Connect to the last version
Schedule Apex tests Execution & Report
Create a Copado API key for Copado user (was not existing)
Recreate copado credentials for copado user (service account) and make them default (int, uat and copado), and not owned by an account which is not a service account
ensure only one default credential per org
align org ids (after past refreshes)
create a list view for default credentials
Avoid creation of user stories in Copado
I have deleted the “New” button in the user stories list view
Additionally, I have created a Flow that will prevent users from creating user stories manually in Copado (in case someone likes the idea of re-adding the “New” button). This flow will validate that the user story being created/updated has not been created by a user that is not the automation user (which is used in the Jira<->Copado connection).
The best way to get IT support is to use the new
Service One Platform.