Our organization is currently using sonarquiew to fail to make automated build by SACM, our quality gate Firing is when there are open or reopening problems (with understanding that a person needs to fix the problem or "accept" before releasing the build). Unfortunately, there are concerns that we are delaying code promotion for issues regarding code formatting and other minor crimes. Also, we need a much more manual intervention than originally expected.
We want the problems of certain sections to trigger a build failure, but "new issues" burn only once. Later on the automated build they are no longer new, so they will not hit the gate.
Is it equal to making anyway, "Break open the building if there is more open / re-opening braking / more important issues"?
Edit: Sorry, I forgot to mention that we have issues of "confirmation" of about 15 who are serving as our backlog so non-new issue filters do not work Apart from this, I am open to minor changes in my workflow.
What I think, the following configurations should do:
No comments:
Post a Comment