Must-share information (formatted with Markdown ): which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension): SonarQube Enterprise Edition Version 8.0 (build 29455) what are you trying to achieve Consistent Quality Gate behaviour what have you tried so far to…

Quality Gate for Short Lived vs Long Lived vs Master Branch

dlow (David Low) February 7, 2020, 4:34am 9

That is also what we wanted - “unit test failure as quality gate to prevet merging a PR”. I have made a suggestion for it to be added. Unit Test Conditions on New Code Quality Gate

1 Like

Topic		Replies	Views
Why don't Unit Test failures show up in short term branches? SonarQube Server / Community Build	20	4458	June 18, 2024
Quality gate pass on some branches by fail on others SonarQube Cloud maven , scanner , gitlab , sonarqube-cloud	5	1291	June 17, 2022
Long lived branches: quality gate does not fail in first analysis SonarQube Server / Community Build branches , bug-no-category	3	2708	April 22, 2020
Code coverage on branches does not break quality gate SonarQube Server / Community Build java , branches , coverage , jacoco	30	12535	August 26, 2019
QualityGate wrong result on short-lived branch SonarQube Cloud gate , sonarqube-cloud	2	617	December 7, 2020

Quality Gate for Short Lived vs Long Lived vs Master Branch

Related topics