Solutions for publishing AMI's from Jenkins

[John]

Hello,

I'm using Jenkins to build and deploy large variety of projects.  Most are written in Python, Groovy, Java or Javascript (Node).  

For a long list of irrelevant reasons, I'd like to start deploying my projects as AMI's as well as docker images.  Basically, if all goes well, we'd be able to grab an AMI, spin up an EC2 instance with it, and have a running instance of the app.

Is there a standard way to go about constructing AMI's with Jenkins?

I see that Packer seems fairly popular:  https://www.packer.io

Thanks,

-John

[Dirk Heinrichs]

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of John

> Is there a standard way to go about constructing AMI's with Jenkins?

 

No, don't think so.

 

> I see that Packer seems fairly popular:  https://www.packer.io

 

This is what we do here, too. It's basically a bunch of Ruby code around Packer and Puppet to prepare the build.json file as well as some Puppet manifests from predefined templates and then start a bunch of threads which run Packer, one for each AMI we create. There might also be a Jenkins Plugin for using Packer directly, just check the plugins.

 

The nice thing about packer is that it can produce all sorts of images, like Docker, Amazon, etc...

 

HTH...

 

                Dirk

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/70d8b1eb-dfff-430c-8e6c-b0e9a105391d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rohit dogra]

Packer is really a good open source tool to build machine images for multiple platforms. Thats one of the reason it’s being popular apart from that it’s lightweight. It uses Json as base and when it comes to building images Packer is able to use different tools to install software onto a image.

There were either no existing tools to automate  the creation of machine images or they had too high of learning curve. The result is that, prior to packer, creating machine images threatened the agility of operations teams, and therefore wasn’t used, despite the massive benefits.

Ref : https://www.packer.io

--