You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Sonarqube 7.3 Developer Edition (with branch plugins) and I use this plugin (version 4.0.0) to report the issues introduced in a Merge Request directly into GitLab.
I want to avoid the merge on GitLab if the pipeline is broken, but I would like to break the pipeline only with a customised Quality Gate (let's say, no BLOCKER or CRITICAL, but allow up to 3 MAJOR issues).
I know I can configure that limits (like setting sonar.gitlab.max_blocker_issues_gate), but it works only with preview mode, and if you have any issue (even a INFO), the hardcoded Quality Gate will break the build.
I'd like to introduce a new parameter to the plugin (let's say sonar.gitlab.ignore_quality_gate=true) that ignores the Quality Gate status when reporting the pipeline status to GitLab.
Cheers
The text was updated successfully, but these errors were encountered:
Thinking better on this issue, there's already a property to set the Quality Gate Failure Mode.
Currently, the supported options are ERROR and WARN. What about this property support the mode NONE, so the Quality Gate is ignored for breaking the build.
Hey there,
I'm using Sonarqube 7.3 Developer Edition (with branch plugins) and I use this plugin (version 4.0.0) to report the issues introduced in a Merge Request directly into GitLab.
It works great, but as we know, Sonarqube branch plugin has some limitations, like a hardcoded Quality Gate for short-lived branches (https://docs.sonarqube.org/7.4/branches/short-lived-branches/).
I want to avoid the merge on GitLab if the pipeline is broken, but I would like to break the pipeline only with a customised Quality Gate (let's say, no BLOCKER or CRITICAL, but allow up to 3 MAJOR issues).
I know I can configure that limits (like setting
sonar.gitlab.max_blocker_issues_gate
), but it works only with preview mode, and if you have any issue (even a INFO), the hardcoded Quality Gate will break the build.I'd like to introduce a new parameter to the plugin (let's say
sonar.gitlab.ignore_quality_gate=true
) that ignores the Quality Gate status when reporting the pipeline status to GitLab.Cheers
The text was updated successfully, but these errors were encountered: