...
Ongoing
- Investigation about ZScaler as a replacement to Virtual Machine
- Centralization of Copado projects into 1 single project (simplifying all operations)
24th July - New Org Pipeline
ICARE
...
Ready to be used
...
Item | Status | Priority | Business Value | Approx. Delivery |
Copado - “Deploy” quick action | DONE | 1 | Simplify the deployment process to developers, reducing the number of clicks and required thinking, making it faster overall.
| Oct 18, 2024 |
Copado - Estabilization of Jira <-> Copado Integration (1 remaining bug) | DONE | 1 | Reduce interruptions of work to developers due to integration issues. There is currently one known issue. | Nov 1, 2024 |
DONE | 1 | Save RM time from having to run the apex tests manually in each of the orgs and create a report to follow-up with the TLs to fix it. This is all automated in this action and only requires follow up by the RM | ||
Gitlab - Running basic validation upon Gitlab Pull Request Creation (Code review process) - Part 1 & Part 2 | DONE | 1 | Prevent merge of user stories for which the deployment won’t work, therefore saving time to developers resolving these as soon as possible. | Nov 15, 2024 |
DONE (Strategy in place) | 2 | Reduce time required by developers and release managers to ensure correct profiles deployment Reduced number of bugs in UAT or PRODUCTION created due to hacks or incorrect conflict resolution (due to the previous point). | Nov 15, 2024 | |
Copado - Optimize Git Repository Performance | DONE | 2 | Faster Copado performance, both for developers during the build process and for release managers during release activitie. | Nov 15, 2024 |
Copado - Provide templates for existing manual tasks automation (during deployment) | DONE | 2 | Reduce time required by release managers in releases to perform manual tasks (by automating these). Reduce error-prone activities to release managers. | Nov 1, 2024 |
COPADO - Enable devs to run INT and UAT Dec 2, 2024validations | DONE | 2 | Wins:
Important
| |
Copado - Code review as a Quality Gate before deployment (implementation) | DONE | 3 | By performing a code review of the changes before deployment, we reduce the number of bugs delivered from the beginning and therefore | Nov 29, 2024 |
Generic - Approval process to grant “Admin” privileges for INT, UAT and PROD orgs (icare and core) | UAT TESTING | 3 | Streamline the process to request Admin privileges in the important orgs.
| Nov 29, 2024 |
DONE | 3 | As output of this investigation we would understand how much time we would save from release manager / developers using this functionality, and/or other benefits. | Dec 13, 2024 | |
DONE | 3 | As output of this investigation we would understand how much time we would save from release manager / developers using this functionality, and/or other benefits. | Dec 13, 2024 | |
DONE | 3 | Reduce the time required by the release manager after deployments to INT, UAT or PROD, where the release manager is currently posting comments for every Jira ticket. | Dec 13, 2025 | |
Copado - Setup Static code analysis monitoring, create reports of the existing situation | TODO | 4 | Reduce the technical debt, which directly influences the time required by developers to modify/create logic in the application, being more efficient/faster. | Dec 27, 2024 |
TODO | 4 | As output of this investigation we would understand how much time we would save from release manager / developers using this functionality, and/or other benefits. | Jan 10, 2025 |
Ongoing
Conversations with Copado
- Discussion Copado ↔ Manuel, on Rollback, Bundle, Copado next-gen, and how Copado can support in the future
- Meeting on Thursday 24th October, questions: https://docs.google.com/spreadsheets/d/1lhtKxmncuf1xjS2f1NswiaYOBNIe7AgcEiV5ffMoUBQ/edit?gid=977593521#gid=977593521https://docs.google.com/spreadsheets/d/1lhtKxmncuf1xjS2f1NswiaYOBNIe7AgcEiV5ffMoUBQ/edit?gid=977593521%23gid=977593521
- Copado GPT https://beta.gpt.copado.com/, https://docs.copado.com/articles/#!copadoai-publication/introduction-to-copadogpt
Activation of Manual Sync of Manual Tasks, bugs around this functionality were raised and fixed
-------------------------------------------------------------------------------------------------------------
October
ICARE - Perform Samosa Retrofit to missing dev sandboxes
New projects into copado: CM Leads & SP26 (Both ICare)
-------------------------------------------------------------------------------------------------------------
September - Main improvements
TECHNICAL - COPADO & JIRA Integration: Automate Manual Tasks sync into Copado
iCARe Retrofit Samosa to Monthly Dev 2 (required by Yash for CM Leads project)
-------------------------------------------------------------------------------------------------------------
August - Main improvements
TECHNICAL - COPADO: Documentation on Profiles and Permission set changes - Way to proceed
TECHNICAL - COPADO: Scheduled back-promotions
iCARe TECHNICAL - COPADO: Include Jira Key in copado commit (Gowtham request)
TECHNICAL - COPADO: Centralize projects to avoid promotion complexities [feedback from Bart]
-------------------------------------------------------------------------------------------------------------
July - Overall improvements
TECHNICAL - COPADO: Remove “Add Metadata” quick action button from User Story
iCARe Update Copado Admin / System access
Apex Tests as deployment quality gate
New Release Management procedure
Centralizing and creating Documentation about Copado Way of Working and the new release management procedure → CRM - Technical Release Management
-------------------------------------------------------------------------------------------------------------
June
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.
...
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
- Created Jira <-> Copado Integration
--------------
...
In essence, to synchronize any user story / task / bug or subtask, make sure of the following:
...
-----------------------------------------------------------------------------------------------
May
...
...
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
...
...
...