|
||||||||
|
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/d/optout.
I think both ideas model the solution the wrong way around. Basically, certain slaves cannot act as the coordinator for any job. So I really wouldn't want to add that restriction to every job on our server. And each time we add or change the slave setup we would have to do this again. Instead I just want to mark certain slaves as being an unusable at all apart from performing specifically designated tasks.
As far as I can see, the Exclude Flighweight Task plugin somehow allows to do this.