We just moved our repo from Azure DevOps to GitHub. Our organization in SonarCloud is still linked to Azure DevOps and we would like to have it unlinked so that we can then link it to GitHub. This would allow us to keep the history and billing in place.
I found some other topics where you did the unlink for other users.
The only way to have your organization bound to a different DevOps Platform currently is to create a new organization and re-import your repositories there. Unfortunately, that means you’ll lose the results of previous analyses on these projects.
If you have a yearly subscription for your current organization, a new coupon can be issued for your new organization by reaching out to your sale representative.
If you have a monthly subscription by credit card, you can simply stop your subscription on the old organization and re-subscribe on the new one.
Hello, thank you for your answer. Creating a new organization and re-import my repositories would mean loosing previous analysis history, which would be very bad.
Is there any safe way, to move a project without loosing its analysis history to the new organization?
Please remember, we just moved our git-repo from azure devops to github, so we only want to change the source where the source code lies, so that the sonar scanner could access the source from the changed repo-url.
I do not understand, why there is a change of organization necessary for that.
Thank you for your reply. That’s really not pleasing, but one more question: Is there a way to keep read-only access to the analysis history in the old organization?
You’re not going to like this answer either: You can keep it as long as you’re willing to pay for it.
There is no “read only” status in SonarQube Cloud. Either it’s live (and charged for) or it’s… gone. (The third option would be to make all the projects public, but I’m sure that’s not an option here.)