[JIRA] (JENKINS-40936) Milestone should be able to abort older builds when reaching the same milestone

[pw...@cloudbees.com (JIRA)]

Title: Message Title

Patrick Wolf commented on JENKINS-40936   Re: Milestone should be able to abort older builds when reaching the same milestone Depending on how many commits and runs are stacked up the lock step from the lockable resources plugin could help here: milestone() lock(resource: 'my-pipeline', inversePrecedence: true) { milestone() input "proceed?" } In this case all of the builds will still stack up at the lock but they will get aborted much quicker. Assume you have 6 commits: Build 1 will enter the lock and wait at the input. All other builds after that will wait at the lock. When Build 1 passes the input the newest build waiting at the lock (say Build 5) enters the lock, passes the new milestone and waits at the input. As soon as Build 5 passes the new milestone all other builds (Builds 2,3,4) are aborted while Build 5 waits at the input This doesn't eliminate the queue but it can dramatically reduce it if you have several builds waiting. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.