Yes, apart from the issue I mentioned, haven't had a chance to look through existing issues yet to see if it is reported.
On Tuesday, August 14, 2012 9:21:21 PM UTC+1, rusty wrote: > > so..... f I understand this completly > If I "Block build when downstream project is building" Jenkins will > resolve all of the downstream builds recursively allowing all children as > well as grandchildren projects to be built before building project 1 again > with different parameters? > > On Tuesday, August 14, 2012 11:31:36 AM UTC-6, cjo wrote: >> >> >> If all of the builds are triggered by project 1, and you only want to run >> one set of parameters at a time through the chain at a time. >> You should be able to use the "Block build when downstream project is >> building" and "Block build when upstream project is building" advanced >> options on all of the projects which will enforce this behaviour. >> >> Doing this will allow you to add Project1 to the queue multiple times >> with different parameters but only have one run for each set of parameters. >> Warning: We found an issue with this if a downstream project is blocked >> (waiting for a resource/slave to come online) which will allow Project 1 to >> run again. >> (Due to fix for https://issues.jenkins-ci.org/browse/JENKINS-8929) >> >> We ran this for several months without problem and in some cases had 5-10 >> instances of Project 1 queued with different parameters. >> This was needed as we had a dependency between multiple projects needing >> to share workspaces, due to the SCM and size of the project we were using >> along with the 30 different build configurations. >> >> Chris >> >> On Tuesday, August 14, 2012 5:54:20 PM UTC+1, rusty wrote: >>> >>> 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 <[email protected]> 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 <[email protected]> kirjoitti 14.8.2012 >>>>> kello 5.39: >>>>> >>>>>
