Hi, Just a quick note: for Jenkins, see here: https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin
Btw, this plugin is subject to deprecation, the Throttle Concurrent Build plugin is advised as a replacement. My 2 cents 2013/11/5 Ginga, Dick <[email protected]> > You might try the Hudson Locks and Latches > plugin<http://wiki.hudson-ci.org/display/HUDSON/Locks+and+Latches+plugin>. I > use it because I have created core build jobs that will build a variety > of product from the same workspace and I only want one going at a time. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Eric Wood > *Sent:* Tuesday, November 05, 2013 8:21 AM > *To:* [email protected] > *Subject:* Re: What is teh best way to prevent several jobs from running > at once? > > > > Scott: > > > > I'm going to look at the throttle plugin, but can you tell me how I set up > a build executor and only create a single agent within my existing running > version of Jenkins? I'm not sure it you are talking about a whole new > installation on jenkins on a different server, or if there is a way to set > up a new executor in Jenkins and a new agent and assign only a single agent > to that executor all in a single installation of jenkins. > > > > Can you clarify? > > > > Thank you, Eric > > > > On Monday, November 4, 2013 4:42 PM, Scott Evans <[email protected]> > wrote: > > Eric, > > If you don't care the order that they run, just that they don't run > simulatnously, my first thought is to set up a build executor with only one > agent, and assign this job to that single executor. That way, only one can > run at a time. There's also a build throttling plug-in, but I haven't > looked at that to know if it would work in your case or not. > > Scott > > > > On Mon, Nov 4, 2013 at 3:36 PM, Eric Wood <[email protected]> > wrote: > > I have about 6 jobs that all deploy to a SalesForce cloud instance and > they cannot run at the same time. This are CI jobs that get triggered by > check-ins to the repository. What is the best way in Jenkins to make sure > that one one job at a time is running and other jobs get queued up to run > once that job completes. > > > > Thanks, Eric > > -- > 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/groups/opt_out. > > > > -- > 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/groups/opt_out. > > > > -- > 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/groups/opt_out. > > -- > 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/groups/opt_out. > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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/groups/opt_out.
