Problem statement
Gowtham was trying to backpromote a set of user stories and getting a strange error in https://syensqo-icare.lightning.force.com/one/one.app#eyJjb21wb25lbnREZWYiOiJvbmU6YWxvaGFQYWdlIiwiYXR0cmlidXRlcyI6eyJhZGRyZXNzIjoiaHR0cHM6Ly9zeWVuc3FvLWljYXJlLS1jb3BhZG8udmYuZm9yY2UuY29tL2FwZXgvZGVwbG95bWVudD9pZD1hM0FQSDAwMDAwM1ZydngyQUMmc2ZkY0lGcmFtZU9yaWdpbj1odHRwcyUzQSUyRiUyRnN5ZW5zcW8taWNhcmUubGlnaHRuaW5nLmZvcmNlLmNvbSJ9LCJzdGF0ZSI6e319
Fix - TL;DR;
The content of the "System admin lite" profile in the branch was not correct, due to wrongly resolved conflicts (by some developer in the past, not necessarily by Gowtham).
I (as release manager) have removed the previous conflict resolutions done manually (this has to be done by a release manager), and created a new deployment, which then will show the conflicts to be resolved one more time (therefore being able to fix the previous resolution).
Troubleshooting process (includes all verifications done)
I went into the promotion branch (accessible from the deployment page), and checked the content of the profile, understanding that the issue was in line 1101 (can be seen in the error) and by doing a blame we can see that the error comes from "Copado Smart resolution", which basically means that copado is applying a conflict resolution that a developer has provided manually in the past.
Is the problem/blocker due to Copado?
No
Is the problem due to a bad practice?
Partially - It's due to a wrong conflict resolution, this can happen to any dev, just let the release manager know, so the previous conflict resolution can be deleted and the developer can re-do the conflict resolution.
Is the problem due to an incorrect configuration of Copado?
No
Lessons learned
Inconrrect conflict resolution can happen to the best minds, just let the release manager know, so the previous conflict resolution can be deleted and the developer can re-do the conflict resolution.
The best way to get IT support is to use the new
Service One Platform.