I migrated from Managed Package DevOps Center to Next Generation Dev Ops Center. Now I am not able to activate pipeline or re-authenticate the Source Control Repository. The branch associated with UAT and Prod seems to be OK, because when I click on the branch it opens OK in GitHub. I am having difficulty is selecting a branch for Integration stage.
Have anyone got any tips for me to follow, thank you so much.
#DevOps Center
Hi Mitesh, this is a known DevOps Center limitation — the "Use an Existing Branch" drop-down doesn't always list every branch in the repo, which is why you can't pick your Integration branch even though it exists. Workaround: on the Integration stage's environment click Edit Branch, pick ANY branch under "Use an Existing Branch" and Save; then click Edit Branch again, choose "Create a branch for me from this stage", type the EXACT name of your existing Integration branch, and Save. Because DevOps Center won't allow duplicate branch names, it finds and reuses that existing branch instead of creating a new one — then you can Activate the Pipeline. If activation still fails, re-authorize the source control connection (Setup > DevOps Center — reconnect the GitHub repository so the OAuth token carried over from your managed-package migration gets refreshed). If this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂
