Quality Gate Rules not getting applied on the Build Pipelines

We are using the Sonar Qube Version :10.2(Its is Enterprises licenses)
Sonar Scanner version in Azure DevOps Task version updated i.e. v5 also we are also using the Build Break extension i.e. SonarQube build breaker (SonarQube build breaker - Visual Studio Marketplace).
We are looking to block the Build which are not satisfying the Quality Gate Rules define for the Build Pipeline.

we have tried with this option ,but the Build breaker is not working as required.

like below pages :Azure build breaker on quality gate failure , CI integration overview and Many others .

we wanted if any Azure DevOps Build Pipelines are not satisfying the Quality Gate the Build should not move ahead and its should be failed or Blocked. Developers should look to fix the define Categories of the Quality Gate Rules.

Hey there.

  1. You may want to open an issue with the maintainer of GitHub - simondel/sonar-buildbreaker-vsts: VSTS task to break your build when you failed the quality gate if you can’t get it working
  2. You can also use sonar.qualitygate.wait=true in your analysis (adding it as an analysis parameter to your Azure DevOps build definition) in order to wait for the Quality Gate result (and break the build if it’s a failure). This is also mentioned in this documentation you linked.

Hi Colin ,

You can also use sonar.qualitygate.wait=true in your analysis (adding it as an analysis parameter to your Azure DevOps build definition) in order to wait for the Quality Gate result (and break the build if it’s a failure) - this is also not working , we checked with this, its not helping us

You’re going to have to go into detail about how you tried to use it, what logs you saw, etc… “It’s not working” doesn’t tell us much.

we have applied this wait timing on Sonar scanner , but the Build pipelines are not breaking which are not satisfying the Quality Gate . we are looking to implement the Build Stop if Quality Gate rules are applied the DevOps Pipelines should fail the Build itself.

the Quality Gate says its failed , but on the Azure DevOps Build is scuuessfully.