Setting up the GitLab integration at the global level

This section explains how to set up GitLab and SonarQube for global integration. To perform this setup, you need the global Administer System permission in SonarQube.

Verifying the server base URL

For the GitLab integration to work:

• The SonarQube server base URL must be a public URL.
• If you want to delegate the SonarQube user authentication to GitLab: you must use HTTPS. This means that the SonarQube server must be secured behind a proxy.

You must configure your SonarQube server base URL in SonarQube, otherwise, integration features will not work correctly.

To verify the server base URL configuration in SonarQube:

• Go to Administration > Configuration > General Settings > General > General and check the instance's Server base URL. 

Setting up the import of GitLab repositories

With this setup, users will be able to import GitLab repositories into SonarQube.

This integration is performed through a “GitLab Configuration” record, which is used in SonarQube to access the GitLab instance. You need the Administration System permission to set up a GitLab Configuration.

To set up a GitLab Configuration in SonarQube:

1. In the SonarQube UI, go to Administration > Configuration > General Settings > DevOps Platform Integrations. 
2. Select the GitLab tab and click Create configuration. The Create a configuration dialog opens.
3. Specify the following settings:
   • Configuration Name (Enterprise and Data Center Edition only): The name used to identify your GitLab configuration at the project level. Use something succinct and easily recognizable.
   • GitLab URL: The GitLab API URL. We recommend using https://gitlab.com. You can also use your own GitLab server URL.
   • Personal Access Token: GitLab token used to connect to the GitLab user account used to report the quality gate status to pull requests. See below.
4. Select Save configuration.

Setting up user provisioning and authentication

See GitLab authentication.