-
New Feature
-
Resolution: Fixed
-
Major
-
None
The current limits in the EC2 plugin bases the limits upon overal EC2 instances. In environments where EC2 is used for things other than Jenkins build slaves, this kind of limit is not useful. There may be any number of instances running in an EC2 account that are not related to performing builds and should not be counted towards this limit.
The EC2 plugin should only count the instances that it creates and destroys, likely by tracking instance IDs.
Ideally there would be an overall global limit set, but the plugin doesn't currently have a global config section, so that may be prohibitively complicated to implement to support this one feature. With a global limit as well as per-cloud limits, one could set a global limit of say 15, and then have two clouds with a limit of 10, so each one could spin up as many as 10 boxes. If one already has 10 going though the other gets stopped at 5.
Looking at the existing structure, it may be better to improve the Cloud-level limit so that it (optionally with a check box?) tracks only build hosts, and then add the per-AMI limits as suggested in JENKINS-6676, with the global limit being added at a later date as more global config options are needed.
- is related to
-
JENKINS-6676 Support instance caps based on a user-defined tag
-
- Open
-
I like the idea of the node cap applying only to instances that Jenkins has started itself. Simply ignore any other instances.