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

New nodes are launched when labels changed in EC2 configuration

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When the set of labels is changed for a configured slave in the EC2 plugin's global config (under "Configure Jenkins"), it forgets about existing nodes and launches new ones.

      It should instead relabel existing nodes with the new labels on first launch. Or at least terminate the old nodes. As it is, you land up with a bunch of duplicate nodes.

      Observed with idle timeout enabled, and stop on idle enabled, with nodes idled down at the time of configuration change.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            francisu Francis Upton
            Reporter:
            ringerc Craig Ringer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: