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
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 defect.
It simply doesn’t work with Quality gates that have new conditions, as the definition of new
See all the details in this thread
I’m quite disappointed that this shortcoming has not been taken into account
The proposed workaround - means using pull requests instead - is a hack, but no solution.
You have to set sonar.pullrequest.key and sonar.pullrequest.branch,
(sonar.pullrequest.base is default = master).
Using a dummy pullrequest key leads to
Also users won’t accept this, they are used to branch analysis works fine with
simply using sonar.branch.name - why do i have to fake a PR ?
Please bring back
sonar.branch.target with default = master to make it work again.