We recently upgraded to SonarQube 10.7 Developer edition, moving from free version 10.0. Our “web” project is currently set up as a “local project” linked to our on-prem GitHub instance. We want to leverage the “DevOps Platform Integration” feature in SonarQube.
Our “web” project contains history and metadata. Re-creating the web project using DevOps Platform Integration would mean that we’d lose history and metadata.
Question:
Is there a way to convert or migrate an existing “local project” to a DevOps-integrated project without losing existing database data?
Alternatively, can a new DevOps-integrated project be set up to inherit or import data from the original “web” project?
Any guidance on preserving our data during this transition would be greatly appreciated.
from my experience with Azure DevOps integration, it is no problem at all.
Just create the DevOps platform integration in SonarQube and service connection in Azure DevOps (I don’t know the corresponding name in GitHub).
Then you can go in your project in SonarQube and set there the connection to your repo.
With the next analyses the links and reporting worked for us, it is even possible to have SonarQube Quality Gate required or optional in pull requests.
Thank you for the prompt reply, Volker (as a new user I am unable to mention your handle). I appreciate it.
We have this existing “web” project that is linked to our GitHub. If we use DevOps Platform Integration for GitHub, it will create a new project with the name of the repository, which is fine. And you are saying that we don’t need to worry about moving metadata from web to the new project? It will just happen? I’ll give that a try to see how it goes. I do worry about the LOC limitation. We have a 2M LOC limit per our license. If I have two projects (web and the new one), we’ll go over 2M unless SQ is able to figure out that it is the same codebase.