DevOps Zone is brought to you in partnership with:

Mitch Pronschinske is a Senior Content Analyst at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. Mitch is a DZone Zone Leader and has posted 2574 posts at DZone. You can read more from them at their website. View Full User Profile

5 Steps for Continuous Deployment

10.19.2011
| 5823 views |
  • submit to reddit
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.