[
https://issues.jenkins-ci.org/browse/JENKINS-11582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159214#comment-159214
]
rsandell commented on JENKINS-11582:
------------------------------------
Experimental fix released in Gerrit Trigger 2.4.0, but it is not working fully
as intended, JENKINS-12152 could have something to do with it. But I need help
in debugging this.
> Allow subsequent patchsets to cancel running/pending builds triggered for a
> change
> ----------------------------------------------------------------------------------
>
> Key: JENKINS-11582
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11582
> Project: Jenkins
> Issue Type: Improvement
> Components: gerrit-trigger
> Reporter: R. Tyler Croy
> Assignee: rsandell
>
> Our tests are long running which means we might have a 15-20 minute
> turn-around on pre-testing commits in Gerrit.
> In the cases where a developer quickly realizes their error, and submits a
> patchset 2, while a patchset 1 is already running wastes a *lot* of Jenkins
> slave resources.
> Ideally when I upload Change 13, patchset 2, all pending or running jobs
> triggered off of Change 13, patchset 1, should be cancelled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
