We have been using SonarCloud with all of our private projects hosted on GitHub.com and use GitHub to authenticate our users.
We are now in the process of migrating our projects away from GitHub.com to an on-prem GitLab. Since our projects are directly tied to GitHub.com today is it possible to migrate the existing projects, one at a time, from their current place and tie them up with our private GitLab solution?
The GitLab server is managed by a larger organization and is not on the public internet, so we do expect that some features will not be able to be ported but we would hope that we can maintain the history of the projects as part of the migration.
Is this something that is going to be offered in the future?
One option would be to keep the old and new projects in parallel but that would double our LoC counts and push us over our tier limit. Would it be possible to at least keep the old projects ‘archived’ as read only and not counting towards the LoC count?
Unfortunately, we do not officially support GitLab server yet in SonarCloud. If you want to stay up-to-date in this regard, you can vote for this portal card.
You can however still run the analysis and keep the history of your projects if you unbind the organization from GitHub.com by deleting the installed SonarCloud app in GitHub. You can then modify your pipelines’ setup to support the new used CI and the only functionalities you will be missing would be the PR decoration and autoscan.
Which platform will you use to authenticate your users?
It is good to know we can still have some analysis even though we will not have the PR integration anymore. It seems that in the best cases the Sonar findings will no longer be usable in PRs which would remove some of the compliance checks we use SonarCloud for.
Does SonarQube provide integration with on-prem GitLab? If so we might be able to use that path.
For user authentication we currently use Okta but we will likely migrate to Active Directory.