So assign the jobs to run on a slave with only 1 executor. I guarantee only one at a time will run.
-- Sami rusty <rustystotallyfakeemailaddr...@gmail.com> kirjoitti 14.8.2012 kello 19.54: > The problem is that I can have no concurrency in between the two top projects > nor any child projects that they have. I have looked at throttle builds > plugin, but it doesn't provide what I need which is full atomicity on the top > level builds and all recursive underlying builds. > > On Tuesday, August 14, 2012 10:37:05 AM UTC-6, sti wrote: > All the builds will enter the queue at the same time, but how many will > actually run in parallel depends on how many executors you have or if you > have used other means of concurrency control like Throttle Concurrent Builds > plugin. > > -- Sami > > rusty <rustystotallyfakeemailaddr...@gmail.com> kirjoitti 14.8.2012 kello > 19.26: > >> >> I am already using a multi-configuration project, I think that the >> disconnect is stemming from how do I use multiple axis to accompolish this. >> >> Won't adding another axis start the two projects in parallel? I can't have >> two projects in paralelll... >> >> On Tuesday, August 14, 2012 3:06:38 AM UTC-6, sti wrote: >> Use a multi-configuration project with one, two or more axes. >> >> -- Sami >> >> rusty <rustystotallyfakeemailaddr...@gmail.com> kirjoitti 14.8.2012 kello >> 5.39: >>
