Another option is to use the build-matrix. If you are performing the same job, but from different machines, then the Matrix may be a good choice:
https://wiki.jenkins-ci.org/display/JENKINS/Building+a+matrix+project I hope that this helps. Mgimza On Mon, Sep 24, 2012 at 10:48 AM, Mark Waite <markwa...@yahoo.com> wrote: > You can either create a multi-configuration job and use that to launch on > multiple nodes, or you could create dedicated jobs for each configuration > and restrict them to run only on the node you specify for that job. > > A multi-configuration job has the benefit that it is a single job, polling > the source master and operating on all machines with a consistent launch, > using the same source code submission for all the jobs. You can select the > nodes to use by node name, or by a label applied to the node (geographic > label that you apply to each node, for example). > > I like multi-configuration jobs. They work very well for me. > > Dedicated jobs are easy to create because you can copy your existing job > and change its definition to restrict it to run on only the specific node > you want. If this is a short term investigation and you'll not use the > configuration long term, it may be a little faster to copy the jobs than to > create and manage a multi-configuration job. > > Mark Waite > > > ------------------------------ > *From:* Chris Withers <ch...@simplistix.co.uk> > *To:* jenkinsci-users@googlegroups.com > *Sent:* Monday, September 24, 2012 4:32 AM > *Subject:* forcing a job to run on a variety of slaves > > Hi Guys, > > I have a job which currently passes on a UK-based machine but which fails > on a US-based machine. > > How can I set up a job such that for each trigger it will run on a > UK-based node *and* a US-based node? > > cheers, > > Chris > > -- Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > > >
