Add the ability to programatically update the AMI ID using Groovy

[marvinpinto]

This is a proposed fix for JENKINS-28268

Our Use Case

At FreshBooks, we have multiple Packer jobs that build new Jenkins build workers as and when the underlying repos are updated. The problem with this approach (currently) is that after this is done, someone needs to go in and manually update the Jenkins configuration to point to the new AMI ID.

Proposed Fix

With this approach, we could trigger a post-build Groovy script to automatically go in and update the relevant AMI ID without us having to do this manually.

Groovy Example

Here is an example Groovy script that demonstrates getting and setting the AMI ID programatically:

import jenkins.model.*;
import hudson.plugins.ec2.*;

Jenkins.instance.clouds.each {
  if (it.displayName == 'test-cloud') {
    it.getTemplates().each {
      println(it.displayName)
      println("Print current AMI id : " + it.getAmi())
      it.setAmi("ami-4567")
      println("Print current AMI id : " + it.getAmi())
    }
  }
}

Jenkins.instance.save()

Reference

https://issues.jenkins-ci.org/browse/JENKINS-28268

Local Test Results

Results :

Tests run: 54, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:19 min
[INFO] Finished at: 2015-07-05T11:57:36-04:00
[INFO] Final Memory: 39M/588M
[INFO] ------------------------------------------------------------------------

[buildhive]

Jenkins » ec2-plugin #123 SUCCESS
This pull request looks good
(what's this?)

[buildhive]

Jenkins » ec2-plugin #124 FAILURE
Looks like there's a problem with this pull request
(what's this?)

[jenkinsadmin]

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

[emoshaya]

This solution fixes the exact same issue we're having at NewVoiceMedia where we have a number of CI Packer Jobs creating base AMI's for existing AMI templates in Jenkins. We're also having to manually update the configuration with the new AMI IDs created from the packer jobs. This will be a great addition hopefully to get merged soon.

Thanks

[fonsecas72]

+1 this would be great! thanks!

[marvinpinto]

Thank you for merging this so quickly! 😄

[francisu]

Thanks for your contribution.

Sent from my iPhone

On Jul 5, 2015, at 17:22, Marvin Pinto notifications@github.com wrote:

Thank you for merging this so quickly!

—
Reply to this email directly or view it on GitHub.

[lielran]

+1

At Kenshoo we update the ami manually(After a packer job that built the slaves) till now.

Thanks for this PR!

[marvinpinto]

If this is helpful to anyone else, this is the python script we use to cleanup and update the AMI IDs.

https://gist.github.com/marvinpinto/a6c9b5119d418a65d489

[fonsecas72]

Thanks again @marvinpinto 👍

[ghost]

@francisu is there a release planned soon ?
this feature would help us a lot

[francisu]

Just did the release, should be available in a day or so.

[ghost]

Got it, thank you!

[burukuru]

The script is a bit out of date and didn't work for me so I updated it and wrote up some instructions here https://github.com/burukuru/jenkins-update-ec2-ami