|
||||||||
|
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.
Seems fixed since 1.427. Note that putting node temporarily offline means no further builds will be scheduled on that node. There is no guarantee that Jenkins will not interact with the slave in any other way. Also, creating random content in node workspace (Jenkins can not get rid off) should generally be discouraged.