Thanks for the replies! Looks like quite a few choices, all of which look pretty good.
Thanks again, John On Wed, Nov 7, 2012 at 9:08 AM, Josselin Pierre <pierre.j...@gmail.com>wrote: > There is also the build flow plugin > https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin > > or even simply the built-in "trigger/call another job" step. =) > > > 2012/11/7 Marek Gimza <marekgi...@gmail.com> > >> Another alternative is to use MultiJob plugin >> >> https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin >> >> >> ... >> Mgimza >> >> >> On Wed, Nov 7, 2012 at 11:57 AM, Josselin Pierre >> <pierre.j...@gmail.com>wrote: >> >>> Hi, >>> >>> You could give a try to the Join plugin, especially since you have a >>> parent job : >>> https://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin >>> >>> >>> On Wednesday, November 7, 2012 5:50:19 PM UTC+1, JohnA wrote: >>>> >>>> I've searched google for this but nothing popped out. >>>> >>>> I have 122 jobs that run automated tests at-xxx. I've created an >>>> at-start job that does some initialization of directories, etc. and I've >>>> trigger the other 122 jobs to start when this one completes. So far so >>>> good... >>>> >>>> The 122 jobs run on a server farm (15 pcs) running jenkins slaves. >>>> Their run time is from 5 minutes to 45 minutes and they are all independent >>>> of each other. So far so good. The entire suite takes somewhere around 3.5 >>>> to 4 hours to run. So far so good... >>>> >>>> I'd like to create at-end, a job that runs when *all* the other ones >>>> are done. Has anyone else done this, and how did you do it? >>>> >>>> John >>>> >>> >> >
