-1

Our organization is currently using sonarqube to fail a SCM triggered automated builds. Right now, our quality gate is firing when there are any open or reopened issues (with the understanding that someone needs to fix or "accept" the issue before the build will continue). Unfortunately, there are concerns that we are delaying code propagation for code formatting issues and other very minor offenses. Also, this is requiring quite a bit more manual intervention than we originally expected.

We want certain classes of issues to trigger a build failure, but the "new issues" filter only fire once. on the subsequent automated build they are no longer new so they no longer fire the gate.

Is there anyway to set up the equivalent to "Break the build if there are more than 0 open/reopened breaking/critical issues."?

EDIT: Sorry, I forgot to mention that we have about 15k "confirmed" issues that is serving as our backlog. so the non-new issue filters wont work either. Also I am open to minor changes to our workflow.

4

1 回答 1

0

据我了解,以下配置应该可以完成这项工作:

在此处输入图像描述

于 2015-03-18T12:22:32.510 回答