|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Great points . . . I have no suggestion for a name shorter than yours.
As I read your reply it occurred to me that perhaps we now need "leave slave for tied jobs only" and "run project per restrictions" both.
That is more than just a documentation issue though that requires a code change for the extra option.
With label expressions, there will is no way to get "tied jobs only" . . . Given that !S02 matches S03, there really is no way to express "leave this node for jobs I specifically put here".
I admit, that for most cases the difference works out and it doesn't matter (because !label is rarely used).
But if I happened to have a Jenkins with !label for a bunch of jobs . . . I really have no way to bring up a new node and keep those jobs off of it while I test and verify the new node. (This feature hole is way beyond the scope of the original ticket, but it does point in that direction.)
The good news of course is that generally I don't have jobs that do things like !S02. Though I guess I could see a job that is !windows (assuming windows is a label) . . . for a shop like mine that is only windows or linux . . . !windows isn't likely. But if you get into an instance where you have multiple linux versions (!ubuntu) or a third OS (like OS/X) this might come up.
I'll leave this all for wiser heads to figure out . . . but I think you are right that our "feature set" has clearly outgrown our current "wording" for the feature . . .
I suspect a full and robust update to both the docs and the feature set would be a pain in the butt without an equal benefit.
Though perhaps some updated docs could at least paper over the issues so it was "good enough".
Frank