Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-6676

Support instance caps based on a user-defined tag

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ec2-plugin
    • 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.

          [JENKINS-6676] Support instance caps based on a user-defined tag

          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.

          Quentin Hartman added a comment - 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.

          Kevin Fleming added a comment -

          There is code in a patch I'm about to send a pull request for that makes per-template instance caps actually work. I don't understand the second comment about 'counting stopped instances', but that could be because it was entered a few months ago. The instance cap calculations do take into account stopped instances.

          Kevin Fleming added a comment - There is code in a patch I'm about to send a pull request for that makes per-template instance caps actually work. I don't understand the second comment about 'counting stopped instances', but that could be because it was entered a few months ago. The instance cap calculations do take into account stopped instances.

          Daniel Aquino added a comment -

          Instances can be tagged so it would be nice if we could set the instance cap based on the tag we give it..

          Daniel Aquino added a comment - Instances can be tagged so it would be nice if we could set the instance cap based on the tag we give it..

            kohsuke Kohsuke Kawaguchi
            abayer Andrew Bayer
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: