Mitch Pronschinske 
5 Steps for Continuous Deployment
Email
The DevOps Zone is
presented by DZone with partners including ThoughtWorks Studios and UrbanCode to bring you the most interesting and
relevant content on the DevOps movement. See today's top DevOps content and be sure to check out ThoughtWorks Studio's Continuous Delivery Whitepapers and UrbanCode's Webinars.
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:
He also give some other details along with a diagram to illustrate on his blog post found here.
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.
Tags:
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
ThoughtWorks Studios and UrbanCode, the sponsors of the DevOps Zone, are champions of the DevOps movement. Their deployment tooling solutions focus on the entire software development lifecycle, involving all parts of an organization, which helps facilitate a migration to the DevOps philosophy.
