|
||||||||
|
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.
This would be very helpful to me as well. I've implemented the slave label axis work-around, but it's a seriously non-scalable hack. It'd be much preferable to have axes represent actual desired configurations, with whatever filters applied, and then separate logic to match enabled configurations with nodes on which to run them.