|
||||||||
|
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.
Jan, that's great and I definitely agree that it's better than where we are right now.
I think it would be better though if we could take advantage of the fact that each AMI has it's own set of Tags and Instance cap! (screenshot here: http://screencast.com/t/zYMzFGti)
I really picture desiring this per AMI config because I may have AMIs that are generic for any job that could spin up dozens of slaves while others that should really only spin up one or two..
What do you think ?