|
||||||||
|
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/groups/opt_out.
This does not work properly still with instance caps: instance caps are calculated solely based on AMI (see EC2Cloud#addProvisionedSlave), not based on template. So, if you have two types of slaves based on a common AMI but intended for different purpose, if the instance cap is low on one type, it may never get provisioned if the other type has many outstanding instances.
I'm not sure an easy way around this particular issue; perhaps the template information could be stored on a provisioned instance as a tag?