Problem statement

I assisted Bartosz to speed up the deployment of https://syensqo-icare.lightning.force.com/lightning/r/copado__User_Story__c/a7ZPH0000001G9B2AU/view to CMINT, understanding and fixing some existing issues during this deployment.

Fix - TL;DR;

  1. There were compilation issues while doing the first validation deployment, therefore Bartosz supported in updating the Apex classes to fix the compilation issues. This was a bit more tricky than expected due to org misalignments in the pipeline. 
  2. There were Apex test issues after fixing the compilation issues, therefore Bartosz supported in Fixing these. The Apex test execution of this story was taking around +20 minutes, due to the scenarions being run in the apex tests.
  3. After fixing compilation & test issues, some merge conflicts appeared and were solved by Bartosz. This can be expected, because 1) this user story has a lot of changes (around 60 apex classes changed), and 2) existing org misalignments
  4. After conflict were solved, the user story was successfully deployed.

Troubleshooting process (includes all verifications done)

Before running any validation deployment or apex tests, I started checking the basics in Copado Important Considerations while Building a User Story, because some of these points were not correct for this user story. For example, the credential being used was not owned by the running user. After these initial checks, we followed the standard steps to build and deploy a user story, also included as part of Copado Guidelines, nothing in special.

The reason why it was complex and tedious to handle this user story is primarily due to the size of it, with around 60 apex classes being changed and with apex tests that took more than 20 mins to run), besides the fact of existing orgs misalignment.

Is the problem/blocker due to Copado?

No

Is the problem due to a bad practice?

No

Is the problem due to an incorrect configuration of Copado?

No

Lessons learned