How to make a branch analysis to always use master as baseline in SonarQube 8.1?

[anon67236913]

Hi,

see this threads for current discussion and status

Howto specify base/target branch

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:/…

Sonarqube 8.1 branch analysis, definition of new ?!

Hi, playing with Sonarqube 8.1 Enterprise, happy to see there’s only one kind of branch now, but … We use a quality gate with only ‘new’ conditions for our java legacy projects. Using a simple Maven project with just one class for the tests. First analysis of master branch gives quality gate OK, as this is the first analysis. This was expected and works similar in our production instance with Sonarqube 7.9.1 Enterprise Now i create some new branch foobar from master and put some sysout int…

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