[
https://issues.jenkins-ci.org/browse/JENKINS-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161982#comment-161982
]
Brian Murrell commented on JENKINS-9531:
----------------------------------------
To add to this, adding a global (i.e. applies to all jobs) level node filter
would be useful with a way for individual jobs to override, append to that
global filter or remove it. The idea being that if I didn't want any jobs to
run on builder3 or builder4 by default, I'd have a global filter of "!lab" but
then jobs that can run on any of the builders can clear that filter so that
they are not excluded by the global "!lab" filter.
> choose matrix build nodes based on label matches
> ------------------------------------------------
>
> Key: JENKINS-9531
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9531
> Project: Jenkins
> Issue Type: Improvement
> Components: matrix
> Reporter: Brian Murrell
>
> With matrix (multiconfiguration) build jobs one can select (groups of) slaves
> to build the job on with the axes. It would be nice if when an axis matches
> multiple nodes (i.e. a label that applies to more than one node, such as
> x86_64) the node list could be further filtered by (not) matching more labels.
> For example, say I have a list of nodes with the following labels:
> builder1: el5 x86_64
> builder2: el5 i686
> builder3: el5 x86_64 lab
> builder4: el5 i686 lab
> If one of my axis specifications is "el5" then any one of the above nodes
> would be selected as a slave to build on. However, what would be nice is to
> have a further filter on the selected nodes, like "lab", so that even though
> the axis specification of "el5" would match any of the available 4 nodes,
> that additional "lab" filter would mean that only builder3 and builder4 are
> eligible nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
