I'm afraid that your solution doesn't work. If A has already started and a new A goes to the queue, the moment A ends and starts to run B, the other A on the queue starts.
On Friday, May 16, 2014 8:54:50 AM UTC+1, [email protected] wrote: > > The > https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Pluginplugin > might do what you want. Define a category to represent the pipeline, > and limit the category to one job only. > > > > *From:* Renato Rodrigues [mailto:[email protected] <javascript:>] > *Sent:* 15 May 2014 17:23 > *To:* [email protected] <javascript:> > *Subject:* Multiple jobs with locks > > > > Imagine the following scenario as a pipeline: > > *Job A > Job B (Build Flow Job) > Job C > Job D* > > Job A is called by a git hook. Job B is a lightweight job that > orchestrates jobs C and D. > > This pipeline works well but I just want only one instance of it at a > time. So if, for example, job C is running and the git hook calls a new Job > A, first the pipeline must terminate after completing job D. > > I've searched some plugins like Locks and Latches or Exclusion plugin but > none have worked. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
