It may not fit your exact needs, but I configured Jenkins such that all
child-jobs spawned/started by a given parent-Job can:
1. Run on any slave
2. Use the same Custom Workspace as set in the parent-Job (has to be
on a shared-drive that is accessible to the slaves)
3. Each child-job sends a
This is my use case:
I have tests that require a collection of machines to run. There are
different types of machine collections, with 1 or more instances of each
type. Each collection can be used by only one driving set of tests at a
time.
The tests themselves do not run in the collection of
Since posting, I've seen that the Metadata
pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Metadata+pluginwould be a
great way to attach the key/values to the slaves instead of the
Slave Setup Plugin. I would still be happy to hear of any ideas on how I
can improve this.
- David
On
I've been looking for a component - or a technique - in which two slaves
can be used for the same job. Since having one job run on two slaves isn't
feasible, it would probably be two (or more) jobs that each start on a
different slave at the same time. Having those jobs start at the same time
