|
||||||||
|
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.
Confirmed on Jenkins 1.577 out of the box. May be an element of randomness to it, as I've had to try twice. The first one (waiting one minute for the slave to come online) didn't work, but the second try (impatiently launched slave manually via web UI) worked.