|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
This issue would appear to be related:
https://issues.jenkins-ci.org/browse/JENKINS-12240
...but suggests a desire for the opposite behaviour: as many configurations of a particular job as possible should run on a node.
However, I'm sure there are just as many people who want the behaviour I'm describing, here's an example:
https://issues.jenkins-ci.org/browse/JENKINS-13619