Setting up Bitbucker Server integration at global level
Setting up Bitbucket Server or Data Center and SonarQube Community Build for integration at the global level.
Prerequisites
You’ve set a SonarQube Community Build base URL in SonarQube Community Build: see Server base URL.
Step 1: Create a Personal Access Token
You must provide a Bitbucket Server / Data Center Personal Access Token that will be used by SonarQube to report the quality gate to the pull requests. This token will be stored in SonarQube and can be revoked at any time in Bitbucket Server / Data Center.
To generate the token, we recommend using a dedicated Bitbucket Server / Data Center account with Administrator permissions. In any case, the account must have the Read permission for the repositories that will be analyzed.
If you want to enter the token in SonarQube in encrypted format, you can encrypt this token.
See Sensitive settings for more information about settings encryption.
Step 2: Create a Bitbucket configuration record
This integration is performed through a "Bitbucker Configuration" record, which is used in SonarQube to access the Bitbucket Server or Data Center instance.
To set up a Bitbucket Configuration in SonarQube:
In the SonarQube UI, go to Administration > Configuration > General Settings > DevOps Platform Integrations.
Select the Bitbucket tab and click Create configuration. The Create a configuration dialog opens.
Select Bitbucket Server.
Specify the following settings:
Configuration Name (Enterprise and Data Center edition only): The name used to identify your Bitbucker configuration at the project level. Use something succinct and easily recognizable.
Bitbucker Server URL: Your Server or Data Center instance URL. For example,
https://bitbucket-server.your-company.com.Personal Access Token: The token you generated in Step 1.
Select Save configuration.
Related pages
Last updated
Was this helpful?