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 blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

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.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}