|
||||||||
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.
Looks great!
Makes sense. Jenkins doesn't consider them equal either despite Label implementing Comparable.
Makes sense. Since it groups by label, it's clear that labels may be inverted (only those "NOT something"), or even useless (label||!label and similar, less obvious rules).
Not sure what you mean. If the node is called 'foo' and you specify '!foo' as label, it'll run on any other node (!windows could be a shortcut for e.g. osx||linux||solaris in a particular setup). If OTOH the node is called '!foo' because the naming conventions don't take label expressions into account (didn't check whether that's possible though), reporting that would be useful. Seems related to similar reports of brokenness related to labels.
Personally I find these list view lists very noisy and would prefer a minimal view similar to what is shown on the label index page for exact matches, but I recognize that's subjective and your use case may even require it to look like that.