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 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 (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 *Sent:* Tuesday, March 24, 2015 12:19 PM *To:* jenkinsci-users@googlegroups.com *Subject:* Is this the correct way to manage multiple SCM triggered builds? For reference I'm on Jenkins 1.601 with Perforce Plugin v1.3.27. I have a polling interval set for H/5 * ... for Perforce SCM changes on a Job in Jenkins. I also have enabled concurrent builds for the job. If multiple checkins occur during the polling interval then multiple instances of the Job are started. The odd part is one job has all of the changes and the others are no different than the first. What I would like to see is either one job started for each changelist (so they all get verified with tests) or one job started for all changes submitted in the interval only. It seems like either solution would require a separate job to poll Perforce then run a script to analyze the changes and spin up any other job(s) rather than relying on the Perforce SCM Plugin + Jenkins internal logic. Is this correct? Thank you, Brent -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/VKiSWK5Nwb0/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NET https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NET?utm_medium=emailutm_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCQcTOoOyvnGPOxPCA1zcMdvcGOj%3DLso_%2BZ%2B3WjDS%3DPvyQ%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCQcTOoOyvnGPOxPCA1zcMdvcGOj%3DLso_%2BZ%2B3WjDS%3DPvyQ%40mail.gmail.com?utm_medium=emailutm_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzOtCJ4Oa84f1pMMs-UzyCVL%2BNgYuP492kHQjAbL4Et-w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 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.commailto:dick.gi...@perkinelmer.com wrote: 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.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com] On Behalf Of Brent Scriver Sent: Tuesday, March 24, 2015 12:19 PM To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: Is this the correct way to manage multiple SCM triggered builds? For reference I'm on Jenkins 1.601 with Perforce Plugin v1.3.27. I have a polling interval set for H/5 * ... for Perforce SCM changes on a Job in Jenkins. I also have enabled concurrent builds for the job. If multiple checkins occur during the polling interval then multiple instances of the Job are started. The odd part is one job has all of the changes and the others are no different than the first. What I would like to see is either one job started for each changelist (so they all get verified with tests) or one job started for all changes submitted in the interval only. It seems like either solution would require a separate job to poll Perforce then run a script to analyze the changes and spin up any other job(s) rather than relying on the Perforce SCM Plugin + Jenkins internal logic. Is this correct? Thank you, Brent -- 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 jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/VKiSWK5Nwb0/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NEThttps://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NET?utm_medium=emailutm_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 jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCQcTOoOyvnGPOxPCA1zcMdvcGOj%3DLso_%2BZ%2B3WjDS%3DPvyQ%40mail.gmail.comhttps://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCQcTOoOyvnGPOxPCA1zcMdvcGOj%3DLso_%2BZ%2B3WjDS%3DPvyQ%40mail.gmail.com?utm_medium=emailutm_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513AEB%40AMERMBX02.PERKINELMER.NET. For more options, visit https://groups.google.com/d/optout.
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 (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 *Sent:* Tuesday, March 24, 2015 12:19 PM *To:* jenkinsci-users@googlegroups.com *Subject:* Is this the correct way to manage multiple SCM triggered builds? For reference I'm on Jenkins 1.601 with Perforce Plugin v1.3.27. I have a polling interval set for H/5 * ... for Perforce SCM changes on a Job in Jenkins. I also have enabled concurrent builds for the job. If multiple checkins occur during the polling interval then multiple instances of the Job are started. The odd part is one job has all of the changes and the others are no different than the first. What I would like to see is either one job started for each changelist (so they all get verified with tests) or one job started for all changes submitted in the interval only. It seems like either solution would require a separate job to poll Perforce then run a script to analyze the changes and spin up any other job(s) rather than relying on the Perforce SCM Plugin + Jenkins internal logic. Is this correct? Thank you, Brent -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/VKiSWK5Nwb0/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NET https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NET?utm_medium=emailutm_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKuUXCQcTOoOyvnGPOxPCA1zcMdvcGOj%3DLso_%2BZ%2B3WjDS%3DPvyQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
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 Sent: Tuesday, March 24, 2015 12:19 PM To: jenkinsci-users@googlegroups.com Subject: Is this the correct way to manage multiple SCM triggered builds? For reference I'm on Jenkins 1.601 with Perforce Plugin v1.3.27. I have a polling interval set for H/5 * ... for Perforce SCM changes on a Job in Jenkins. I also have enabled concurrent builds for the job. If multiple checkins occur during the polling interval then multiple instances of the Job are started. The odd part is one job has all of the changes and the others are no different than the first. What I would like to see is either one job started for each changelist (so they all get verified with tests) or one job started for all changes submitted in the interval only. It seems like either solution would require a separate job to poll Perforce then run a script to analyze the changes and spin up any other job(s) rather than relying on the Perforce SCM Plugin + Jenkins internal logic. Is this correct? Thank you, Brent -- 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 jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com?utm_medium=emailutm_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E513ACE%40AMERMBX02.PERKINELMER.NET. For more options, visit https://groups.google.com/d/optout.
