Unfortunately that will end in the same result. If a new SCM build is queued before the previous pipeline is done (regardless if that is from a poll or a push), then I'm in this situation.
On Monday, August 1, 2016 at 5:20:58 PM UTC-5, Mrinal Mukherjee wrote: > > Hi Chris, > > This may not be the solution you are looking for. Do you think using a > webhook (to trigger a job when a change is pushed to source control) would > be a better bet than a poll SCM option? > > Mrinal > > On Tue, Aug 2, 2016 at 9:26 AM, Chris Shannon <[email protected] > <javascript:>> wrote: > >> I have a set of builds chained together using the Parameterized Trigger >> Plugin. The starting build polls SCM and then kicks off build/test/deploy >> jobs which all run on the same node and reuse the same codebase established >> in the SCM job. >> >> This seems like a pretty standard/basic thing, but I'm running into a >> problem keeping the SCM poll job from running again until all of the builds >> in my "pipeline" are complete. If the poll job wakes up, it will insert >> itself in the queue before some of my test/deploy jobs, change the >> underlying SCM codebase, and royally mess things up. I've looked at >> plugins like Build Blocker and Lockable Resources, but none of these seem >> to handle these triggered jobs (they can handle jobs that are already >> queued, but not jobs yet to be triggered). >> >> I think that I'm doing something basic here - what am I missing? Do I >> really need to write to lock files on my hard drive to handle this? >> >> Note that I'm not using Jenkins pipeline/workflow because it does not yet >> support ClearCase, but I realize that life would probably be easier if I >> was... >> >> Thanks! >> >> -- >> 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:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/4d84c91d-3327-434f-a195-61d2a46ac221%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/4d84c91d-3327-434f-a195-61d2a46ac221%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2b53e90c-37eb-47ca-b755-d50fd8afe3c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
