My team has a setup where source code is in GitHub and CI/CD pipelines in Azure DevOps.
As we’re moving more toward an agentic dev workflow (AgentEx) - we have focused on shifting-left all feedback as early as possible to allow the agent (and devs) to correct issues before issuing a PR. The team has found (by experimenting with our open-source SonarQube Cloud orgs) that it’s ideal to bind the org to GitHub and use the node-based SonarQube Cloud analysis to run during the build (@ sonar/scan), ensuring consistency in both the analysis that runs locally as well as on cloud-based CI/CD build agents. (We use the Azure DevOps SonarCloud build-breaker plugin to check for SonarQube Cloud result status after pipeline build)
Unfortunately, our corporate (non-open-source) org is bound to Azure DevOps and cannot be unbound via the SonarQube Cloud web UI.
It would be less than ideal to switch bindings by having to go through the process of setting up a new SonarQube Cloud organization bound to GitHub, configure billing for it, then decommissioning our existing Azure DevOps-bound organization.
Can you please provide guidance on migrating our organization’s AzureDevOps binding to GitHub while retaining the same SonarQube cloud organization (and no billing headaches)?
our open source repos: (for reference)
our corporate org:
- ECFMG