We’re currently in the process of migrating our GitHub repositories to a new organization. While we’ve successfully installed the SonarQube app in the new GitHub organization.
If we configure SonarCloud with the current organization name “xyz-new” and later rename it to “xyz” after the cutoff date, can we able to simply unbind and rebind the integration or Is it feasible to point the existing sonarqube to new github organization?
@sonarsourcers Appreciate some guidance on this. To give more clarity on this requirement.
Currently our GitHub organization (named xyz) hosted in GitHub.com which SonarCloud is installed.
We are planning to migrate to GitHub EMU with same name (xyz)
Approach is , first create a new org with name xyz-new in GitHub EMU.
Migrate all of repos in to new org xyz-new in GitHub EMU
Once migrated, rename the old github organization from xyz to xyz-old and rename the new github organization xyz-new to xyz.
So the final github organization name would be same “xyz”. Please confirm, what are all the changes would be required.
Also noticed at project level, cannot be migrated and require to reimport at new organization which will cause no historical analysis ?
Bumping a thread usually isn’t needed. We just don’t work on the weekends, like lots of people.
The name of the org isn’t too important here. You’ll need to rebind your org (uninstall the SonarQube Cloud app on the old org, install it on the new one via your SonarQube Cloud global Adminitration > Organization settings > Organization binding).
Once that is done, you’ll need to one-by-one refresh your project bindings.
My gut is telling me that turning off GitHub Member Sync if it’s turned on (docs) is a smart move just to be sure nobody gets yoinked from the org before you’re ready. Disabling this will not remove any members from your org, just stop the sync of new members. I’ll follow up on this (to see if this is a useful recommendation) but I won’t have an answer right away!
If it’s not enabled, no action there.
Refreshing project bindings will not cause you to lose any project history. It just makes sure your projects are bound to the right repo so that thinks like PR decoration work.
Hey Colin,
In the existing Sonarcloud account, i am using personal github username and in that we cant see the EMU org while trying to bind. So is there anyway we can transfer the sonar cloud account to the new github EMU org.
If we create new sonarcloud org then can we transfer the billing from old org to new org
To proceed, you’ll need to add an account with access to the EMU organization to your SonarQube Cloud organization as an org admin. This will allow you to trigger the binding process from that account.
Yes. Issue is resolved I was able to add new github user and able to bind the new github org.
Thanks @Colin for helping out here. We can close this thread
Appreciate and thanks for the reply.