|
||||||||
|
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.
Actually, this seems to happen for any job in the queue, even if it's waiting for a different kind of slave to spin up...
Again, on Jenkins v1.565-1.1
This did not happen when I was on v1.560 & before.