Sonarqube Developer Edition Branch Analysis

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  • what are you trying to achieve
  • what have you tried so far to achieve this

Sonarqube Version 8.2.0.32929 Developer Edition

How exactly does it work with the Branch Analysis only manually with the sonar.branch.name parameter? I have integrated Bitbucket Server when I create a new project in Sonarqube only the Master Branch is there.

Hello @Jon.Walter

Indeed using the sonar.branch.name parameter is the way to go for branch analysis.
The integration of our scanner in different ALM will automatically handle this parameter (in Azure DevOps or GitLab for example). Though this is only valid when they have a pipeline feature to run the scanner, which is not the case of BitBucket server.

For BitBucket Server, the integration will help you to:

  • set your project up by importing it (name, ID, etc.)
  • have PR analysis working (the communication between SQ and BB works)

But there is nothing that will scan your project. So it means that you need to execute a scanner (locally or in a CI) that will checkout your code and analyze it. It’s here that you will use sonar.branch.name to scan different branches and make SonarQube aware of it.

Does it make things clearer to you?

Thanks for the reply yes that answers my question