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

Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves

      The EC2 plugin works great for dynamically provisioning EC2 slaves (as needed) when their label is specified under "Restrict where this project can be run," but it doesn't do anything if that label is passed in using a NodeLabel parameter. Note that this only seems to affect the EC2 provisioning step; jobs set to run on a slave via NodeLabel parameter will happily run on provisioned-by-EC2-plugin slaves that are already around.

          [JENKINS-25963] Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves

          Andrew Bayer added a comment -

          This is the case with anything using NodeProvisioner - i.e., any cloud slave plugin. This is because NodeLabel doesn't actually tell the queue anything about what it needs, exactly - if it had a LabelAssignmentAction, that'd work.

          Andrew Bayer added a comment - This is the case with anything using NodeProvisioner - i.e., any cloud slave plugin. This is because NodeLabel doesn't actually tell the queue anything about what it needs, exactly - if it had a LabelAssignmentAction, that'd work.

          Trevor Baker added a comment -

          I see the same problem with the "Throttle Concurrent Builds" plugin when you throttle across jobs with a category.

          https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin

          Trevor Baker added a comment - I see the same problem with the "Throttle Concurrent Builds" plugin when you throttle across jobs with a category. https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin

            Unassigned Unassigned
            dimaspivak Dima Spivak
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: