|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [JIRA] (JENKINS-7683) "Restrict where this... d...@gweep.net (JIRA)
- [JIRA] (JENKINS-7683) "Restrict where... kbertel...@java.net (JIRA)
- [JIRA] (JENKINS-7683) "Restrict where... d...@gweep.net (JIRA)
I am encountering this same problem; however, it is not the parent job that it is the problem, it is that all of my matrix jobs are running on the master when I want them to run on specific slaves.
On other jobs, I set the 'Restrict where this project can be run' to "NODE1 | NODE2 | NODE3" (etc), and the job runs on whichever system is available.
When setting up a matrix job, I see no way to do this except to create an additional axis. But, if I do that, then I get a two-dimensional matrix, and each of my configurations runs once on each host.
What am I supposed to do in this situation?