Re: Is this the correct way to manage multiple SCM triggered builds?

Which is typically why you set polling for `@daily` and use push notification as the primary driver On 24 March 2015 at 16:30, Brent Scriver bscri...@phxlabs.ca wrote: Cool, thank you! I take it that won't work though if Jenkins is unavailable for some reason however right? While polling

RE: Is this the correct way to manage multiple SCM triggered builds?

That’s true, if my Jenkins is ever down, I have a problem. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brent Scriver Sent: Tuesday, March 24, 2015 12:30 PM To: jenkinsci-users@googlegroups.com Subject: Re: Is this the correct way to manage

Re: Is this the correct way to manage multiple SCM triggered builds?

Cool, thank you! I take it that won't work though if Jenkins is unavailable for some reason however right? While polling would pick up changes when Jenkins returns? Thank you! Brent On Tue, Mar 24, 2015 at 12:22 PM, Ginga, Dick dick.gi...@perkinelmer.com wrote: A Perforce-side trigger

RE: Is this the correct way to manage multiple SCM triggered builds?

A Perforce-side trigger (change-submit) would run once for each checkin and provide the single associated changelist to sync to. I think this will give you a one-to-one job execution From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brent Scriver