[JIRA] (JENKINS-56178) Offer to select a specific build as the new reference in "reset" quality gate

[luebbe.opensource@gmail.com (JIRA)]

Lübbe Onken created an issue

Jenkins / JENKINS-56178 Offer to select a specific build as the new reference in "reset" quality gate Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-18 08:59 Priority: Minor Reporter: Lübbe Onken Currently the "reset" quality gate selects the next successful build as the new reference no matter how good it is. Add an option to make the selected build the new reference, because its quality is already known. It probably only makes sense to allow the last build in a sequence of failed builds to become the new reference, because otherwise you would have to recalculate the quality gates for all following builds up to the last build. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[fitzner@ifao.net (JIRA)]

R. F. commented on JENKINS-56178

Re: Offer to select a specific build as the new reference in "reset" quality gate Concerning your statement:

"It probably only makes sense to allow the last build in a sequence of failed builds to become the new reference, because otherwise you would have to recalculate the quality gates for all following builds up to the last build."

I don't know how difficult it is (CPU intense for Jenkins?) to recalculate the quality gates for all following builds up to the last build, but from a user point of view: As soon as the pipeline measures more issues because a new tool is detected used by the git repository then it is quite possible that the defined quality gate will always fail. This is a gap in the plugin. It is not possible to define tool-specific quality gates (new feature!) but apart from that image a project which needs a little bit more flexibility and then a PO comes along and says that is also good enough that is our baseline for now. But on a develop branch the developer push quickly. So choosing the last one would be maybe not right one. Why not choosing the first unstable / failed one after the latest successful build? Also I'd like to know if the "reset quality gate" button could be restricted to certain user/group configurable via Jenkins access control?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[fitzner@ifao.net (JIRA)]

R. F. edited a comment on JENKINS-56178

Re: Offer to select a specific build as the new reference in "reset" quality gate

Concerning your statement: "It probably only makes sense to allow the last build in a sequence of failed builds to become the new reference, because otherwise you would have to recalculate the quality gates for all following builds up to the last build." I don't know how difficult it is (CPU intense for Jenkins?) to recalculate the quality gates for all following builds up to the last build, but from a user point of view:

As soon as the pipeline measures more issues because a new tool is detected used by the git repository then it is quite possible that the defined quality gate will always fail. This is a gap in the plugin. It is not possible to define tool-specific quality gates (new feature!) but apart from that image , imagine a project which needs a little bit more flexibility and then a PO comes along and says that is also good enough that is our baseline for now. But on a develop branch the developer push quickly. *So choosing the last one would be maybe not right one. Why not choosing the first unstable / failed one after the latest successful build?*

Also I'd like to know if the "reset quality gate" button could be restricted to certain user/group configurable via Jenkins access control?

Add Comment