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 into code to provoke an issue.
But the analysis behaves exactly as the master branch, means the quality gate is OK !?
With Sonarqube 7.9.1 this would have been a short-lived branch with quality gate failed
because of 1 issue.
Put another sysout into code and do another scan for foobar branch => quality gate fails
because of the 1 new issue.
So it is possible to create a branch from master and put a lot of issues in it, but quality gate
will be always OK for the first branch analyis.
If the next analysis brings new issues the quality gate will fail.
But what about the issues from the first branch analysis ?!
When using another quality gate without ‘new’ conditions it works fine.
So how should that ever work with a quality gate using ‘new’ conditions ?
I thought the definition of new = the git changeset from branch master to branch foobar !?
Is it possible to change this behaviour ?
If not, this is a bug / showstopper IMO. Can’t update to Sonarqube 8.1, as this will not work for us.