|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This issue still exists in the 1.21 code. It looks like it also trickles down to the individual server-type definitions, where the "instance cap count" is generated by looking for the # of instances running a particular AMI image.
Instead, the EC2 plugin should simply tag the machines with identifiers, and be able to search for them that way. It should also be able to recover lists of live running EC2 slaves by searching for these nodes with these tags.