Changing your project binding

In SonarQube Server 2026.5, you can bind an unbound project and you can change the binding of a bound project.

You must be an administrator of your project.

Unbinding or changing the binding of a bound project

1. Retrieve your project. For more information, see Retrieving projects.

2. Go to Project Settings > General Settings > DevOps Platform Integration.

3. In the bottom of the page, select Reset. The project is unbound.

4. To bind the project to another repository, see Binding an unbound project.

Binding an unbound project

If you created your project manually, you can bind it to its DevOps platform repository to benefit from the features of a bound project.

To bind a project to a GitLab, Azure DevOps, Bitbucket Cloud, or Bitbucket Data Center repository, you need an access token stored in SonarQube Server for your user account: an API token for Bitbucket Cloud, or a personal access token for the other platforms. The credentials set on the global DevOps platform integration are not used for this, so you can only bind projects to repositories you have access to on the DevOps platform. If no token is stored for your user account, saving the binding fails with the message personal access token for '<configuration name>' is missing.

To store a token for your user account, do one of the following:

• Start a repository import through Create project and select your DevOps platform. Before it lists your repositories, the import flow prompts you for a token.

• Call the POST api/alm_integrations/set_pat web API endpoint while signed in as the user who will save the binding. That user account needs the Create Projects permission. Set the almSetting parameter to the name of the DevOps platform configuration and the pat parameter to a valid token. For Bitbucket Cloud, also set the username parameter to the email address of your Bitbucket account.

To bind the project:

1. Retrieve your project in SonarQube Server. For more information, see Retrieving projects.

2. Select Bind project. It's available on both of these pages:

   • The Overview page, which opens when you retrieve the project.

   • The Summary page, which shows the quality gate status and the analysis results. Go to Your project > Analysis > Summary.

   The DevOps Platform Integration page opens.

1. In Configuration name, enter the Configuration record used to manage your DevOps platform integration at the global level. Ask your system administrator.

2. This step depends on your DevOps platform:

   • GitHub: In Repository name, enter the name of the GitHub repository you want to bind. You can enable the analysis summary under the GitHub Conversation tab.

   • Bitbucket Data Center: In Project key and Repository slug, enter the project key and the repository slug of the Bitbucket Data Center repository you want to bind. Both are part of the repository URL: .../projects/<key>/repos/<slug>/browse.

   • Bitbucket Cloud: In Repository slug, enter the URL of the Bitbucket Cloud repository you want to bind.

   • GitLab: In Project ID, enter the unique identifier of your GitLab project you want to bind.

   • Azure DevOps:

     • In Project name, enter the name of the Azure DevOps project containing your repository.

     • In Repository name, enter the name of the Azure DevOps repository you want to bind.

     • By default, pull request annotations are enabled. You can disable them.

3. Select Save configuration. The new binding is saved.

4. Select Check configuration. SonarQube Server checks if the entered DevOps platform repository exists and you have access to it.

The project binding (incl. the configuration check) is logged in the audit logs.