[
https://issues.jenkins-ci.org/browse/JENKINS-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161681#comment-161681
]
Brian Murrell commented on JENKINS-9531:
----------------------------------------
{quote}
Couldn't you use the label specifier "el5 && lab"?
{quote}
If I could, I would. But I don't see how I could. For matrix jobs, I can add
axes for the various combinations I want built. How do I specify the kind of
free-form eligible node specifier you describe above?
(As I am sure you know, but for the benefit of others reading here) note that
the Combination filter is not the place to do this. That filters the
combinations that will actually be built. I don't want to do that. I want to
filter the nodes that are eligible for any of the given combinations once a
list of nodes has been selected for a given combination.
I might also want to be able to filter on a negative expression like "!lab" so
that some jobs can specify "el5" and be eligible on all 4 builders but others
with '!lab" are not allowed to run on the lab labelled builders.
> 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