Howto specify base/target branch

[cernst (Christian Ernst)]

Need to specify base/target branch for Developer Edition Version 8.1 (build 31237)

• We use the sonar-scanner option -Dsonar.branch.name to specify the branch name.
• We have reported a branch ‘master’ and using the New Code Period setting Previous version (Default).
• For the master branch this works as expected.
• For a new developer branch the first analyses is always PASSED.
• According to some older Sonarqube documentation there was an option ‘-Dsonar.branch.target’, but that was removed in https://jira.sonarsource.com/browse/SONAR-12426
• So how can we tell Sonarqube what base it should use for comparing to ?

[Rebse (Gilbert Rebhan)]

Welcome

see this threads for current discussion and status

Sonarqube 8.1 branch analysis, definition of new ?!

Hi, in the meantime i did several tests with your workaround proposal and … it does not apply. Created a feature request, hope it gets proper attention, as this will hit ALL customers with Developer Edition and higher after updating to Sonarqube 8.1 (i know your official recommendation for Enterprise customers is to stay with LTS version, but i’m sure you’re also interested in Enterprise customers living on the bleeding edge !?) I have used the JGit api, have ideas and would like to help…

Sonarqube 8.1 branch analysis, bring back sonar.branch.target

Hi, using Sonarqube Enterprise since version 5.x With the upcoming of the branching feature we switched from using the LTS version to the most recent version to be able to use branches - we used multiple Sonarqube projects for different branches before. All works fine, after the users had get used to the concepts of short-lived and long-lived branches. I very much welcome the decision to go from short-lived/long-lived branches to a branch is a branch, but the implementation has a serious…

Gilbert