Can the “Throttle Concurrent Builds Plugin" be used to reliably prevent concurrent builds in a multi-server, "build farm" setting?
Can the “Throttle Concurrent Builds Plugin" be used to reliably prevent concurrent builds in a multi-server, "build farm" setting? Example: if the Build Farm consisted of Master Server, Slave Server 1, Slave Server 2, Slave Server 3 - could the master server request three builds, for three versions of the same software, and all these builds (1 per server) would launch concurrently? (Max Concurrent Builds, Max Concurrent Builds Per Node both set to "1"). Also, can the “Throttle Concurrent Builds Plugin" handle load balancing, choosing the "least busy" of the available servers? Or would a build of a given type be launched on the same server where it was most recently launched? -- 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/010e5b7e-7e1a-4d5f-b0a3-9b0857675f88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problem with Throttle Concurrent Builds plugin
I am seeing it not work with Build Flow jobs, either. Jenkins 1.534 Throttle Concurrent Builds version: 1.8 -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Problem with Throttle Concurrent Builds plugin
The differences with my config are: Jenkins 1.509.2 instead of 1.534 (I really want the stability of LTS) Throttle Concurrent Builds version: 1.8 (probably limited because of my Jenkins, i don't see 1.8 as an option in the update center) My jobs are matrix jobs On Thu, Oct 10, 2013 at 3:27 AM, wrote: > That sounds exactly like what I do, and it works for me. I’m using > Jenkins 1.534, and Throttle Concurrent Builds Plugin 1.8 (the latest for > both). This has been working for some time. > > Our jobs are all standard free-style jobs. > > Sorry I can’t give any useful suggestions. > > Matthew > > ** ** > > *From:* jenkinsci-users@googlegroups.com [mailto: > jenkinsci-users@googlegroups.com] *On Behalf Of *Jon Schewe > *Sent:* 09 October 2013 20:10 > *To:* jenkinsci-users > *Subject:* Problem with Throttle Concurrent Builds plugin > > ** ** > > I just installed this today to try and avoid some issues I have with locks > & latches. I have some multi-configuration jobs. I want to allow multiple > jobs to run at the same time, but only 1 job of a given category to run per > node. This sounds exactly like what the plugin was written for. So I went > into my configuration and created a category and set Maximum Total > Concurrent Builds to 0 and Maximum Concurrent Builds Per Node to 1. I then > went to all of my jobs and assigned them to this category and checked the > radio button for throttle as part of one or more categories. > > ** ** > > I then manually started two jobs from the same category to see if one > waited for the other. It didn't work. Both jobs started on the same node. I > also tried settings Maximum Concurrent Builds Per Node in the job itself to > 1 and that didn't help either. > > ** ** > > What am I missing about this configuration? > > > > > -- > > This e-mail and any attachments may contain confidential, copyright and or > privileged material, and are for the use of the intended addressee only. If > you are not the intended addressee or an authorised recipient of the > addressee please notify us of receipt by returning the e-mail and do not > use, copy, retain, distribute or disclose the information in or attached to > the e-mail. > Any opinions expressed within this e-mail are those of the individual and > not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any > attachments are free from viruses and we cannot accept liability for any > damage which you may sustain as a result of software viruses which may be > transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in England > and Wales with its registered office at Diamond House, Harwell Science and > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom > > > -- > 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. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://mtu.net/~jpschewe -- 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. For more options, visit https://groups.google.com/groups/opt_out.
RE: Problem with Throttle Concurrent Builds plugin
That sounds exactly like what I do, and it works for me. I’m using Jenkins 1.534, and Throttle Concurrent Builds Plugin 1.8 (the latest for both). This has been working for some time. Our jobs are all standard free-style jobs. Sorry I can’t give any useful suggestions. Matthew From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jon Schewe Sent: 09 October 2013 20:10 To: jenkinsci-users Subject: Problem with Throttle Concurrent Builds plugin I just installed this today to try and avoid some issues I have with locks & latches. I have some multi-configuration jobs. I want to allow multiple jobs to run at the same time, but only 1 job of a given category to run per node. This sounds exactly like what the plugin was written for. So I went into my configuration and created a category and set Maximum Total Concurrent Builds to 0 and Maximum Concurrent Builds Per Node to 1. I then went to all of my jobs and assigned them to this category and checked the radio button for throttle as part of one or more categories. I then manually started two jobs from the same category to see if one waited for the other. It didn't work. Both jobs started on the same node. I also tried settings Maximum Concurrent Builds Per Node in the job itself to 1 and that didn't help either. What am I missing about this configuration? -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Problem with Throttle Concurrent Builds plugin
I just installed this today to try and avoid some issues I have with locks & latches. I have some multi-configuration jobs. I want to allow multiple jobs to run at the same time, but only 1 job of a given category to run per node. This sounds exactly like what the plugin was written for. So I went into my configuration and created a category and set Maximum Total Concurrent Builds to 0 and Maximum Concurrent Builds Per Node to 1. I then went to all of my jobs and assigned them to this category and checked the radio button for throttle as part of one or more categories. I then manually started two jobs from the same category to see if one waited for the other. It didn't work. Both jobs started on the same node. I also tried settings Maximum Concurrent Builds Per Node in the job itself to 1 and that didn't help either. What am I missing about this configuration? -- http://mtu.net/~jpschewe -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: Throttle concurrent builds plugin
I ahve a situation where matrix job sub job(one per slave) needs to be throttled with free style job, but the free style job can run 4-5 concurrent builds. Looks like throttle does not work for matrix build. or am i wrong. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Throttle-concurrent-builds-plugin-tp3732090p4675876.html Sent from the Jenkins users mailing list archive at Nabble.com. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Throttle Concurrent Builds plugin vs. Exclusion-Plugin
The "Throttle Concurrent Builds" plugin operates at the job level; the "Exclusion-Plugin" operates at the level of the individual step (or range of steps) within a job. The proposed plugin deprecation list (https://wiki.jenkins-ci.org/display/JENKINS/Proposed+Plugin+Deprecation) suggests that the "Throttle Concurrent Builds" plugin might supersede the "Exclusion-Plugin". Is that still the plan? Until that happens, can both plugins be used together? Any suggestions for effective ways to use these plugins are appreciated. Thanks -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Can I replace the "Exclusive Execution" plugin with the "Throttle Concurrent Builds" plugin?
Can I replace the "Exclusive Execution" plugin with the "Throttle Concurrent Builds" plugin? The proposed plugin deprecation list (https://wiki.jenkins-ci.org/display/JENKINS/Proposed+Plugin+Deprecation) suggests that it is possible, but I can't work out how. Thanks -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom