|
||||||||
|
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/groups/opt_out.
I've seen something similar. The instances are configured to stop on idle rather than terminate. The instances still displayed in /computers but were stopped/offline. Jenkins did not start the stopped instances while logging that my instance cap had been reached (which it had). The build remained in the queue since the instance cap had been met AND it was not starting the stopped instances it had previously deployed.