Quality gate failing on master branch even though no changes in master recently but only in feature

We are using a self hosted version of sonarqube.

An intriguing thing is that, quality gates are failing on our main branch. However
there were no changes to main branch of our code(from the time qualitygates were passed on it successfully) but only changes were made to the feature branches.

The change was done in a feature branch, but it got considered by SonarQube and now when building on master, it considers that a change was done compared to a feature branch.

New Code setting for our project is set as the default Previous version from global settings(we have not made any change from the default one)

Ideally we would like to have Sonarqube scans on master branch to fail only if code in master branch is not adhering to quality gates and it should not be dependent on errors/failures/bugs from feature branch code

Any help pn how to achieve this would be helpful

Hey there.

As requested in the template post, what version/edition of SonarQube are you using?


We are self hosting community edition of Sonarqube

What version – this should be in the footer of your instance.

  • Community Edition
  • Version 9.9.1 (build 69595)


So it sounds like all of your analyses are pointing at the main branch of your SonarQube project. In the Community Edition of SonarQube, only analysis of the main branch is supported.

So if you’re running analyses on all branches… stop!