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

Jenkins EC2 Plugin Does not detect already provisioned slaves

    XMLWordPrintable

Details

    Description

      following the provisioning of a Jenkins ec2 instance using the ec2 plugin, we have a Chef cookbook modify the ec2 name tag on that instance so, that it is unique per instance in aws. However, doing this breaks that ability for Jenkins builds to detect this already provisioned instance assigned to its label. When I trigger a build using the label of the already provisioned instance, it spawns a brand new instance instead of using the existing one. I don't see this issue when I change the AWS Name Tag for that instance back to what it's set in the global configuration.

      Attachments

        Activity

          ebrahim_moshaya Ebrahim Moshaya created issue -
          francisu Francis Upton made changes -
          Field Original Value New Value
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 163518 ] JNJira + In-Review [ 208834 ]

          People

            francisu Francis Upton
            ebrahim_moshaya Ebrahim Moshaya
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: