Continuous Delivery

Continuous Delivery
Mike McGarr
mike.mcgarr@excella.com
http://earlyandoften.wordpress.com
@jmichaelmcgarr

About Me
J. Michael (Mike) McGarr
Excella Consulting, Arlington VA
Lead of Excella’s Java Center of Excellence
Java Developer for over 11 years
Interests:
Developer Productivity
XP & Agile
Automation
Testing
Polyglot Programming
2

Agenda
Story
What is Continuous Delivery?
Core Practices
Tools
3

Typical Project
4
Analyst & Customer
Requirements
Architect
Design
Developer
Development
Tester
QA
Operations
Release

5
Waterfall
http://flic.kr/p/6fREaa

6
Problems with Waterfall
Long QA feedback loop
Lack of collaboration
Inability to change direction

WaterFall Project
7
Analyst & Customer
Requirements
Architect
Design
Developer
Development
Tester
QA
Operations
Months!
Release

8
Agile
http://flic.kr/p/PQFQg

Agile Project
9
Customer
& Team
Customer
& Team
Customer
& Team
Requirements
Requirements
Requirements
Test
Test
Test
Development
Development
Development
Operations
Release
Days!
The
Last
Mile?
Months!

10
The Last Mile
Manual Deployments
Insufficient Configuration Management
Infrequent, Error Prone Deployments

11
Stressful Releases

Agenda
Story
Core Practices
Tools
12

13
What is
Continuous Delivery?

…a set of practices and principles aimed at, building, testing, and releasing software faster and more frequently.
16
Continuous Delivery is…

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
- First of the Twelve Principles behind the Agile Manifesto
17

Goals
Cycle Time
Quality
18

“How long would it take your organization to deploy a change [to production] that involves just one single line of code? Do you do this on a repeatable, reliable basis?”
Mary and Tom Poppendieck,
Implementing Lean Software Development
19
Cycle Time

http://flic.kr/p/y8KV8
20
Done means Released

21
Frequent Automated Deployments
http://flic.kr/p/29Ree

22
Continuous what?
Continuous
Delivery
Continuous
Deployment
Continuous
Integration

Agenda
Story
Core Practices
Tools
23

24
Core Practices

25
Continuous Deployment
Build Pipelines
Deployment Automation
Configuration
Management
Continuous Integration
Testing
Agile

26
Configuration Management
Version Everything!
Single Identifier
Dependencies
App Configurations
Data
Environments

27
Continuous
Integration
http://flic.kr/p/5GpzSM

28
Check-in Daily
Commit to Trunk
Automate the Build
Keep the Build Fast
Every Commit results in Build
Test in Clone of Production
Automate Deployment

29
Recommended Practices
Extreme Programming (XP)
Fail a Build for Design Breaches
Fail a Build for Slow Tests
Fail a Build for Warnings & Code Style Breaches

30
Testing

31
Kinds of Tests
Unit Tests
Integration Tests
Functional/Acceptance Tests
Performance & Load Tests
Penetration Tests
Exploratory Tests

32
Testing Strategy
Identify and Prioritize Project Risk
Decide what Actions to Take
Tests = Executable Specifications
Confidence

34
Testing Recommendations
Automate your Tests
Use Fakes/Mocks
Automated Acceptance Testing

35
Automated Acceptance Tests
Fast Feedback
Reduce Tester workload
Testers can do Exploratory Testing
Regression Tests
Requirements can be generated from Tests

Acceptance Test Approaches
Acceptance Test Driven Development (ATDD)
Behavior Driven Development (BDD)
Given [some precondition]
When [some event]
Then [some result]
36

http://flic.kr/p/6VmGxK
37

38
Artifact
Repository
Application
Configurations
Middleware
Version
Control
Operating System
Database

39
Use Appropriate Technology
http://flic.kr/p/6pmtQL

Scripting Approaches
Script logs into each box and runs deployment script commands
Script runs locally, each remote machine has agent execute script
Package app using platform’s packaging technology, and use infrastructure management tools push new versions
40

Database Deployments
Version your Database
Evolve Your Database Incrementally
41

Environment Management
Version your Application Configuration
Version your Operating System
42

43
Deploying to the Cloud
http://flic.kr/p/4R35Dd

44
Build Pipelines
http://www.fotopedia.com/users/chmehl

Build Pipelines
A Build Pipeline is an automated manifestation of your process for getting software from version control into the hands of your users.
45

Synonyms
Build Pipeline
Deployment Pipeline
Continuous Integration Pipeline
Deployment Production Line
Living Build
46

BuildPipelines
A Chain of Jobs
Early Jobs run Fast
Every Check-in creates a new Pipeline
When a Job Fails, the Pipeline fails
Keep Code Production Ready
47

48
Stages of a Pipeline

49
Pipeline Practices
Build Once, Deploy Many
Deploy the Same Way to All Environments
Smoke Test you Deployments
Deploy into a Copy of Production
Each Change should Propagate Instantly
If any part fails, Stop the line

50
Pull System

51
Continuous Deployment

Agenda
Story
Core Practices
Tools
52

53
Tools
http://flic.kr/p/5cK2

Version Control
54

Dependency Management
55

Database Management
56

Infrastructure Management
57

58

59
Build Automation

60
Testing Tools

61
Acceptance Test Tools

62
Questions

63
Contact Me
Mike McGarr
mike.mcgarr@excella.com
http://earlyandoften.wordpress.com
@jmichaelmcgarr

http://earlyandoften.wordpress.com	187
url_unknown	6
http://www.linkedin.com	2
http://a0.twimg.com	2
http://translate.googleusercontent.com	1
http://paper.li	1
https://twimg0-a.akamaihd.net	1

Continuous Delivery

by Mike McGarr on Jun 17, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

7 Embeds 200

Statistics

Continuous Delivery — Presentation Transcript