-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Currently, the EC2 instance cap is global, across all instances of all AMIs. More granularity would be nice - i.e., to allow a cap for each instance type, or a cap for each AMI. This would allow for having a larger number of cheap instances and a more limited number of more powerful but more expensive instances.
- is related to
-
JENKINS-14965 Instance limits improvement
-
- Closed
-
Now that we have the ability stop/start existing instances, another nice addition to the instance cap behavior is to have an option to count stopped instances as well as running instances. This would allow for forcing a fixed number of instances to be created, ensuring that a job is always run on an instance with a warm workspace, or queued. In my case, starting a job on a new instance is usually the wrong thing to do because a cold workspace increases by build time by 5 times or more, waiting for a running build to finish is a much better choice.