|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I think I'm hitting the same issue as the original poster. Perhaps I can clarify the failure scenario. Say you have a matrix build called "Matrix", with a single axis of user-defined values "p1", "p2", ... "p5". And say you want all of that build to run on the Master node, and not on another slave node "node1". AFAICS, six tasks are kicked off for such a build - the parent (flyweight) task "Matrix", plus a task for each configuration in the matrix: "Matrix >> p1", "Matrix >> p2", ... "Matrix >> p5". Now, with the "Matrix Tie Parent" plugin, you can succeed in pinning the parent task "Matrix" to the Master node, but this has no effect on the per-configuration tasks "Matrix >> p1", etc. So some of those will tend to run on the slave node "node1". I have not found any way to restrict where these tasks are run, as can be easily done with non-matrix jobs.