• Type: New Feature
• Resolution: Unresolved
• Priority: Major
• Component/s: parameterized-trigger-plugin
• Labels:

  None

[JENKINS-18536] Remove downstream job from queue before new triggers

Markus created issue - 2013-06-28 08:48

Markus made changes - 2015-04-29 07:23

Description

Original: Given two jobs: * Downstream, which has a 60s quiet period * Upstream, which triggers a parameterized build on Downstream Now, if you quickly trigger Upstream 3 times, then there will be 3 Downstream jobs in the queue. They will then all run. We would like parameterized triggering in combination with downstream quiet period to behave sort of like the SVN quiet period behaves: If Upstream is triggered multiple times, then only the last triggered Downstream will remain in the queue. Summary: Before Upstream triggers Downstream, Upstream should remove any instances of Downstream from the queue. This should of course be an option and not the default behavior.

New: Given two jobs: * Downstream, which has a 60s quiet period * Upstream, which triggers a parameterized build on Downstream Now, if you quickly trigger Upstream 3 times, then there will be 3 Downstream jobs in the queue. They will then all run. We would like parameterized triggering in combination with downstream quiet period to behave sort of like the SVN quiet period behaves: If Upstream is triggered multiple times, then only the last triggered Downstream will remain in the queue. This will help when you have limited verification resources during development and would like to run a "best effort" approach. It will prevent the queue from continuously growing. Summary: Before Upstream triggers Downstream, Upstream should remove any instances of Downstream from the queue. This should of course be an option and not the default behavior.

R. Tyler Croy made changes - 2016-07-25 23:50

Workflow

Original: JNJira [ 149843 ]

New: JNJira + In-Review [ 177489 ]