Binding an unbound organization
Binding your unbound SonarQube Cloud organization is slightly different depending on your DevOps platform.
If you created your organization manually, then it’s not bound to its corresponding DevOps platform organization and you don’t benefit from many advantages. This procedure explains how to bind your unbound organization. See Binding with the DevOps platform for more information. To do so, you need the corresponding permissions on your DevOps platform and the Administer Organization permission in SonarQube Cloud enabled. See Managing organization permissions for more information.
You cannot unbind nor change the binding of an organization bound to a GitLab group or an Azure organization.
If the binding fails because the organization already exists in SonarQube Cloud and you’ve lost administrator access to this organization, send a request to contact@sonarsource.com with all the necessary details.
Binding to a GitHub organization
You must be an owner of the GitHub organization.
To a GitHub.com organization
Log in to SonarQube Cloud with your GitHub account. If you’re a member of an enterprise, you may use any of your DevOps Platform accounts or your SSO account. In that case, see Using multiple accounts for important insights.
Retrieve your organization. See Retrieving your organizations for more information.
Go to Administration > Organization settings > Organization binding.
Select the GitHub.com button. The Install SonarQube Cloud page opens. The SonarQube Cloud app is required to allow SonarQube Cloud to access your GitHub organization.
Select the GitHub organization you want to import.
In Repository access, choose which Git repositories the SonarQubeCloud GitHub app can access. The app must have access to a repository for it to be imported to SonarQube Cloud, analyzed, and have its pull requests decorated. If a repository isn't accessible, it won't be available for import or analysis and its pull requests won't be decorated. You can always change this setting later, see Modifying the repository access rights of the organization for more details. For help diagnosing a repository that isn't analyzed or decorated, see Diagnosing missing pull request decoration or analysis.
Select Save. Your SonarQube Cloud organization is bound.
To a GHE.com Cloud organization
This feature is available in the Enterprise plan.
To bind an unbound organization to a GHE.com Cloud organization, you must add it to your existing SonarQube Cloud enterprise if it’s not already there. Proceed as follows:
Create the GHE.com application to be used to bind your SonarQube Cloud organization as described in Step 1: Create your GHE application. You can also reuse an existing one.
Install the application as described in Step 2: Install your app to your GHE organization.
Log in to SonarQube Cloud with your enterprise admin account and retrieve your SonarQube Cloud enterprise.
Go to Organizations.
If your organization is not part of your enterprise, add it as follows. Otherwise, go to the next step. a. Select Add organization. The Add an organization dialog opens. b. Select your GHE.com Cloud organization and confirm. Your organization is now added to your enterprise.
Select your organization from your enterprise list. Your organization page opens.
Select Bind Organization in the header. The Repository binding page opens.
Under GitHub, select GHE.com Cloud. The GitHub app details form opens.
Complete the form with the details of your GHE.com application. See Step 3: Import your GHE.com organization for more information.
Select Bind organization.
Auto-import new GitHub repositories
GitHub.com and GHE.com Cloud both support the Auto-import new GitHub repositories feature. Once your organization is bound, you will see an additional option for this feature. It’s enabled by default. It automatically imports newly added or created repositories in your GitHub organization into SonarQube Cloud without having to go through the manual new project analysis setup flow.
As a requirement, All repositories must be selected in GitHub’s Repository Access settings. See Modifying the repository access rights of the organization for more details.
Existing repositories in GitHub created prior to enabling the Auto-import new GitHub repositories feature are excluded.
Note that a sudden spike in new repositories might cause you to reach your plan limits and pause analysis. Ensure the plan you currently use has enough allowance.
Binding to a Bitbucket Cloud workspace
You must be an administrator of the Bitbucket workspace:
You will already be an administrator of your default workspace.
For any other workspace, you have to add your Bitbucket account to a user group with the Administer workspace user right enabled.
To bind your unbound organization to a Bitbucket workspace:
Log in to SonarQube Cloud with your Bitbucket account.
Retrieve your organization. See Retrieving your organizations for more information.
Go to Administration > Organization settings > Organization binding.
Select the Bitbucket button.
When prompted, grant access to the SonarQube Cloud application to read your Bitbucket Cloud workspace. SonarQube Cloud requests access for:
Reading your account information.
Reading your repositories and their pull requests.
Reading your team membership information.
Binding to a GitLab group
You can bind your SonarQube Cloud organization to:
Any GitLab parent group of which you’re the owner.
Your personal GitLab group. This group refers to the repositories that are under your personal namespace.
To bind your unbound organization to a GitLab group:
In GitLab, create the personal access token required by SonarQube Cloud to access the GitLab group. See Step 1: Create a GitLab personal access token for more details.
Log in to SonarQube Cloud with your GitLab account. If you’re a member of an enterprise, you may use any of your DevOps Platform accounts or your SSO account. In that case, see Using multiple accounts for important insights.
Retrieve your organization. See Retrieving your organizations for more information.
Go to Administration > Organization settings > Organization binding.
Select the GitLab button.
Select either
Import any GitLab group, if you want to import a GitLab group other than your personal one, or
Import my personal GitLab group, if you want to import only the repositories that are under your personal namespace.
In GitLab group key (if you don’t import your personal GitLab group), enter the group key. To retrieve the key, see Step 2: Retrieve the GitLab group key for more information.
In Personal Access Token, paste the personal access token you created in the first step.
Binding to an Azure DevOps organization
You must be an administrator of the Azure DevOps organization.
To bind your unbound organization to an Azure DevOps organization:
In Azure DevOps, create the Personal Access Token (PAT) required by SonarQube Cloud to access the Azure DevOps organization. See Step 1: Create a PAT on the Azure organization for more information.
Log in to SonarQube Cloud with your Azure DevOps account. If you’re a member of an enterprise, you may use any of your DevOps Platform accounts or your SSO account. In that case, see Using multiple accounts for important insights.
Retrieve your organization. See Retrieving your organizations for more information.
Go to Administration > Organization settings > Organization binding.
Select the Azure DevOps button.
Follow the instructions.
In Personal Access Token, paste the PAT you created in the first step.
Related pages
Last updated
Was this helpful?