We have a handful GitLab repos in our organization (around 3000). Far from all are relevant for SonarCloud analysis, we have about 100 repos being analyzed. The problem is creating a new project and binding it, or importing projects.
When importing a project only the name is shown in the list, meaning when there are repos with the same name it is not possible to tell which is which.
When binding in the project settings it’s easier since I can just bind with a repo and see which one the project links to.
Both approaches have the same issue, retrieving the full list of repositories can take several minutes and it often fails (GitLab rate limits? SonarCloud problem?).
Ideally I’d like to do this automatically but it seems SonarCloud doesn’t expose the internal ALM APIs.
Any suggestions on what we can do? Creating separate SonarCloud organizations is one approach but that comes with additional license costs and other problems.
We are aware of the challenges with listing Gitlab repositories for organizations that have a large number of repos. While we still plan to improve this, enhancements for GitLab specifically haven’t been implemented yet. I’ll make sure we include you in the group of users who would benefit from this update.