Controlled AI-assisted delivery, DevSecOps and compliance engineering, written from inside environments where somebody eventually has to answer for the outcome. 6 posts and counting.
Merging Salesforce security metadata does not resolve the disagreement between two branches. It just makes the disagreement happen automatically, on the way to production, with nobody watching. Keep an approved Golden Set in its own branch, overwrite the promotion branch before Salesforce sees it, and there is nothing left to merge.
Real Copado release management is chaos with a suit on. Everything looks mostly green until you hit validate, back promote or prod deploy, and then a component is missing: the team swears it was deployed, the pipeline swears it was validated, and you are stuck in the gap between what Salesforce contains and what Copado believes is in scope.
Most Salesforce DevOps implementations scale people badly. Developers commit locally, Copado wants commits, Azure DevOps runs CI, and somewhere in the middle someone invents a hybrid process that duplicates logic, weakens security and makes scaling the team harder instead of easier.
The Christmas season is in full swing and along with Christmas shopping, its now time to refresh your pipeline. As every Release Manager will know - Christmas is the busiest time of the year.
This is the second article on our introduction to Copado functions series. Last article we showed how to build a function, this article is all about making it run.
Copado Functions can make your DevSecOps/Salesforce job so much easier - lets see how to use them!
