Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

5 Steps for Continuous Deployment

DZone's Guide to

5 Steps for Continuous Deployment

· DevOps Zone
Free Resource

Download “The DevOps Journey - From Waterfall to Continuous Delivery” to learn learn about the importance of integrating automated testing into the DevOps workflow, brought to you in partnership with Sauce Labs.

Peter Blair recently blogged about his thoughts on setting up a CI (he suggests Jenkins) in tandem with a continuous deployment system.  Here was his checklist:

1. Developer commits to git/master


2. CI pulls from git/master

2.1 CI runs all regression tests against git/master

2.1.1 CI returns report to developer and halts if any fail

2.2 CI Looks up the package manifest of a given project, and pushes project to staging server


3. Staging server determines which OS project belongs under (Debian, etc) and generates debootstrap image if none exist

3.1 Staging server creates clone of debootstrap image, and apply all .deb packages from manifest to image

3.2 Staging server stores image to shared file space


4. CI calls deployment server to deploy the image to a given environment


5. Deployment server checks manifest, and determines which class of server image is to be deployed, and attempts to deploy the image to appropriate Dom0 for the given environment, as the appropriate DomU

-- Peter Blair

He also give some other details along with a diagram to illustrate on his blog post found here.

Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure, brought to you in partnership with Sauce Labs

Topics:

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}