Integrate SonarQube with your AI agent, scan for secrets and dependency risks, and explore and manage issues—all from the command line.
Start using SonarQube CLI
Hi, we have TWO paid sonarcloud.io organisations (yeah I know, not handy)
The first and most used one is bound to Github, the second one is not. Because only one binding is possible.
Problem: Someone advertently bound the second one to Github, and thus broke the bounding of the first one.
I am now trying to fix this, but I am stuck:
first I uninstalled the SonarCloud app in Github.
next I started the bounding from the Organization Settings screen in the first SonarCloud instance
when the freshly SonarCloud app in Github redirects back to Sonarcloud, I get a red message popup “ID 123456678 does not exist” and an forever rotating cursor.
when refreshing the page, I go into a dialog to create a NEW sonarcloud instance. There is no option to bind to an existing one.
I’ll admit that I’m a bit confused – and maybe I’m just missing some detail that will make it click.
If I have an organization on SonarCloud that is bound to an organization on GitHub, and I then go to another (manually created) organization and start the binding process… I’m presented with a screen where I can only configure existing applications, not actually attach the application to the GitHub organization (and therefore complete the binding).
I took another route: remove the SonarCloud app from Github. And reinstall it from the Github marketplace. Now I was able to bind to the existing SonarCloud org
Thanx for your (quick) response, it triggered me to explore other ways
