Page Comparison

...

1. Verify your SonarQube server settings in global settings of Bitbucket

2. Run SonarQube source code analysis for main branch

   1. Configure the source code analysis

   2. Analysis results must be visible in SonarQube

3. Configure corresponding SonarQube project in repo settings of Bitbucket

4. Go to source code view and see the existing Sonar issues/stats

   1. You should see the SonarQube statistics and issue annotation

      

   2. Statistics and annotations are missing? Verify your repository configuration:

      1. Did you configure the correct analysis directory?

      2. Does the SonarQube project key match with the configuration in Bitbucket?
         

         Image RemovedImage Added

5. Create a pull request with issues in the code.

6. Run SonarQube source code analysis for source branch of your pull request.

7. 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.

   1. An error

      

      hints at a wrong Sonar analysis configuration or a wrong analysis directory setting

   2. No issue annotations:

      1. Verify that you can see the issues that should be shown in SonarQube

      2. Do the issue annotations appear after clicking “Refreshing Sonar analysis” in the pull request overview? Then check your Webhook configuration

...

• you are using localhost or a wildcard address for Bitbucket which is not supported because SonarQube does not allow these. Please use the real Bitbucket hostname instead.

• you do not have a valid HTTPS certificate for Bitbucket configured in SonarQube's JVM or , see this community article for more information.

• you have invalid proxy settings that prevent SonarQube from connecting Bitbucket. Please see this community article for more information.: check your -Dhttp.proxyHost and -Dhttp.nonProxyHosts JVM arguments