For number one you could also look at the locks and latches plugin and assign each job to have the same lock so only one will run at a time.
https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin Or the Throttle Concurrent Builds plugin which supposedly replaces the locks and latches plugin, but may be overkill to just limit jobs from running: https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin Will On 01/22/2013 09:30 AM, Eric Pyle wrote: Hi Fabian, 1. The simplest solution would be to restrict those "similar" jobs to a single slave, and set up that slave with only 1 executor. 2. There's no way to do this as far as I know. You could achieve something similar if you set up each batch command in a separate job and used the Join plugin to manage them from a single job to start all and another single job to run after all batch command jobs are done. Regards, Eric On 1/22/2013 8:23 AM, Fabian Birk wrote: Hello, I have 2 questions: 1. Is it possible to set up a queue for similar jobs? I want to run many jobs parallel except the jobs which are using the same resource. In CruiseControl.Net you are able to define a queue and the jobs in this queue arent allowed to run parallel. 2. Is it possible to run batch commands parallel in a single job? thank you for reading
