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.
