Timeline for What are best practices and/or tools for updating AMIs on a regular basis?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2017 at 17:13 | history | edited | Michael Pereira | CC BY-SA 3.0 |
comments contain valuable info
|
| Mar 14, 2017 at 22:38 | comment | added | Michael Pereira | Wow thanks a lot for that info, it sounds way better than doing the update in the xml file directly! | |
| Mar 14, 2017 at 22:00 | comment | added | Michael Bravo | if you are building new AMIs via Jenkins itself in any sort of automated way where you can parse the output for the ID, you can update them via postbuild groovy script, see here - github.com/jenkinsci/ec2-plugin/pull/154 | |
| Mar 14, 2017 at 14:42 | history | answered | Michael Pereira | CC BY-SA 3.0 |