|
||||||||
|
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.
I won't call myself a Jenkins expert, but I admin 20 some Jenkins instances, so I'm not novice either.
If the behavior surprised me, I think will surprise most folks.
Don't get me wrong . . . I understand your assertion here about the behavior being correct and expected.
However, I think this !S02 behavior is worth noting in the updated documentation . . . it is a corner case that folks are not likely to think about unless they step directly into the "do do" and find it.
IMHO of course.
Frank