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 wrote:
> There is also the build flow plugin
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
>
> or even simply the built-in
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
> Another alternative is to use MultiJob plugin
>
> https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugi
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 wrote:
> Hi,
>
> You could give a try to the Join plugin, especially since you have a
> parent job :
> https://wiki.jenkins-ci.o
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 auto
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 serv
