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

Criteria based AMI selection

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • ec2-plugin
    • None
    • ec2 1.55

      We are using Hashicorp Packer to build an agent AMI. Right now we need to copy the resulting AMI ID from the build log and update the agent in the settings on the Jenkins master which is painful.

      Packer can scan for AMIs based on a filter and pick the most recent one to base it's build on. Could this be an option here too?

      Would reduce the amount of documentation needed in our and other teams to cover the manual AMI update.

          [JENKINS-59180] Criteria based AMI selection

          James Green created issue -
          Dan Nicholson made changes -
          Assignee Original: FABRIZIO MANFREDI [ thoulen ] New: Dan Nicholson [ danbnicholson ]
          Dan Nicholson made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Dan Nicholson made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Fixed but Unreleased [ 10203 ]
          Raihaan Shouhell made changes -
          Released As New: ec2 1.55
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]
          Raihaan Shouhell made changes -
          Link New: This issue is related to JENKINS-63917 [ JENKINS-63917 ]

            danbnicholson Dan Nicholson
            jmkgreen James Green
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: