Long lived branches: quality gate does not fail in first analysis

SonarQube Server / Community Build
1

Dear All,

Continuing the discussion from old forum:
https://groups.google.com/forum/#!topic/sonarqube/57XrEbTT8dA

I see that following workaround is not quite working strangely:

git checkout master
mvn sonar:sonar -Dsonar.branch.name=my_branch
git checkout my_branch
mvn sonar:sonar -Dsonar.branch.name=my_branch

I see quality gate passed even if there are obvious failures (related to new code coverage and new duplicate codes quality gate conditions) in my branch code. Its only after the next analysis when the quality gate fails if there are more failing changes.

So under that scenario I think https://jira.sonarsource.com/browse/MMF-1265 should get priority as there is no workaround currently to the issue. Or please provide some suggestions/workaround.

We have no idea whether code will pass quality gate before merging. Resolving a sonar issue after merge goes through the usual loop of dev -> review -> merge -> build and so its hard to convince some people to use it.

Thanks a lot,
Kumar

1 Like
2

I fully support @Kumar_Gaurav here. The current behaviour is quite bad.
I also see the problem for long lived branches.

3

Is there any way - with added parameters - to get the same status for a new branch derived from “master” rather than “0 issues”.

4

I would be interested in this as well!