Continuous Delivery with Chef and Go

Not a talk about tools

The tools illustrate the concepts

Continuous Delivery

Build-Test-Release

Deployment Pipeline

Is this change good enough to go Live

Fail Fast, Learn Fast

Don’t wait till Production release

Go Domain Model Concepts

Key to modeling a deployment pipeline

Go Concepts

Traceability

Traceability through Pipeline Labels

Visual Metaphor

Key to visibility and traceability

Build Pipeline• Pipeline per component• Build

– Automated build scripts– Gradle, Simple Build Tool (SBT) etc…

• Test– Automated tests

• Unit, Integration – Junit, Rspec, ScalaTest• Functional – Cucumber + Webdriver

– Test results artifacts• Create artifacts

– Packaged as RPMs• Traceability through pipeline labels

Build Pipeline Demo

Demo App

• 3 Tiers• App• Service 1• Service 2• DB• Siteconfigs – siteconfig.git– For site config changes without requiring app

deployment

Chef

Infrastructure as code

Chef recipe

Templatize Configuration

Install RPMs

Deployment Pipeline Demo

Deployments

• Automated One click deployments triggered from Go• Chef for deployment• Many times a day• Deployment pipeline per environment• Pipeline dependencies help promote binaries from one

environment to another

RPMs ease deployment

Chef + YumApp deploys treated like just another rpm

installationfpm ruby gem

Deploment Pipeline Stages

• Deploy• Upgrade database

– Apply schema changes– Load data

• Post deploy Smoke Test• Manual Signoff Gate Stage

Deployment Notifications in Ganglia

References• http://www.thoughtworks.com/products/webinars/end-

end-automated-build-and-deployment-pipeline-maven-chef-and-go

• http://martinfowler.com/bliki/DeploymentPipeline.html

• https://learnchef.opscode.com/

• www.thoughtworks.com/products/go-continuous-delivery/

Copyrights

• http://cd-with-thoughtworks-go.blogspot.in/

• Thoughtworks Studios

Questions