-
Improvement
-
Resolution: Fixed
-
Minor
-
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.
- is related to
-
JENKINS-63917 Unable to configure ami-id remotely with ec2-plugin
-
- Open
-
We use Packer as well and I find it very inconvenient to have to update the EC2 plugin configuration every time we rebuild the AMI. I believe https://github.com/jenkinsci/ec2-plugin/pull/533 should fix this.