On this page, you find common errors when using the app and how to resolve them.
...
Configuration Checklist
Verify your SonarQube server settings in global settings of Bitbucket
Run SonarQube source code analysis for main branch
Configure the source code analysis
Analysis results should be visible in SonarQube
Configure corresponding SonarQube project in repo settings of Bitbucket
Go to source code view and see the existing Sonar issues/stats
You should see the SonarQube statistics and issue annotation
Statistics and annotations are missing? Verify your repository configuration:
Did you configure the correct analysis directory?
Does the SonarQube project key match with the configuration in Bitbucket?
Create a pull request with issues in the code.
Run SonarQube source code analysis for source branch of your pull request.
Go to the pull request view and check if the Sonar analysis results are visible. You should see a quality gate status overview, and issue annotations in the pull request diff.
An error
hints at a wrong Sonar analysis configuration or a wrong analysis directory setting
No issue annotations:
Verify that you can see the issues that should be shown in SonarQube
Do the issue annotations appear after clicking “Refreshing Sonar analysis” in the pull request overview? Then check your Webhook configuration
1. Sonar issue information not found
...
If you are sure that there is a project in SonarQube with such a key in SonarQube, check the status of the following option selected SonarQube Edition in the repository settings of the Sonar for Bitbucket app:
...
If you use a community edition, the option has to be disabled.
If you use a commercial edition (like developer), this option needs to be enabled.Sonar server configuration:
...
3. No annotations for SonarQube issues within a pull request
...