Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1vn9Zf0. Andy Vaughn gives attendees a case study of how changing the development model and release cycle of a 5 year old software product to continuous delivery greatly improved the product. Filmed at qconsf.com. Andy Vaughn is the lead engineer for executing software designs that concern the entire MindTouch technology stack and cross functional teams.

1. Continuous Delivery Without
Breaking Everything
James Andrew Vaughn (Andy) @MindTouch

2. InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
Watch the video with slide
synchronization on InfoQ.com!
http://www.infoq.com/presentations
/cd-case-study

3. Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
Presented at QCon San Francisco
www.qconsf.com

4. James Andrew Vaughn (Andy)
• Software Engineer at MindTouch
• @modethirteen on Twitter & GitHub
• Professional Interests aside from Continuous Delivery
• Frontend Web Performance & RUM
• Web components (Polymer)
• JavaScript & CSS Pre-processing and Build Automation
• SSO and Identity Management
• Scala

5. Not Sure What This Session Is About?

8. Release
Test
Build

9. 2006
2010
2011
20
20
20
Cloud Infrastructure
Development Begins
MindTouch On
Premise Initial
Release
Tremors of
Continuous Delivery
Manual Cloud
Releases
Quality and Testing
Catch Up
Releases Become
Invisible
On Premise Cloud Enlightenment

10. 2006
2010
2011
20
20
20
Cloud Infrastructure
Development Begins
MindTouch On
Premise Initial
Release
Tremors of
Continuous Delivery
Manual Cloud
Releases
Quality and Testing
Catch Up
Releases Become
Invisible
On Premise Cloud Enlightenment

11. 2006
2010
2011
20
20
20
Cloud Infrastructure
Development Begins
MindTouch On
Premise Initial
Release
Tremors of
Continuous Delivery
Manual Cloud
Releases
Quality and Testing
Catch Up
Releases Become
Invisible
On Premise Cloud Enlightenment

12. 2006
2010
2011
2012
20
20
Cloud Infrastructure
Development Begins
MindTouch On
Premise Initial
Release
Tremors of
Continuous Delivery
Manual Cloud
Releases
Quality and Testing
Catch Up
Releases Become
Invisible
On Premise Cloud Enlightenment

13. 2006
2010
2011
20
2013
20
Cloud Infrastructure
Development Begins
MindTouch On
Premise Initial
Release
Tremors of
Continuous Delivery
Manual Cloud
Releases
Quality and Testing
Catch Up
Releases Become
Invisible
On Premise Cloud Enlightenment

14. 2006
2010
2011
20
20
2014
Cloud Infrastructure
Development Begins
MindTouch On
Premise Initial
Release
Tremors of
Continuous Delivery
Manual Cloud
Releases
Quality and Testing
Catch Up
Releases Become
Invisible
On Premise Cloud Enlightenment

15. V1 V2 V3 V4 V5
On-Premise
Release Cycle
V6 V7

16. Release
Test
Build
On-Premise

17. On-Premise
Build: Development Environments
Image: https://www.flickr.com/photos/kalimistuk/5222488195/in/set-72157594487294945

18. On-Premise
Build: Version Control

19. On-Premise
Build: Continuous Integration

21. Release
Test
Build
On-Premise

23. Release
Test
Build
On-Premise

24. On-Premise
Release: Packaging

25. Release: Supported Platforms
On-Premise

26. On-Premise
Release: Pre-Release Testing

27. On-Premise
Release: Deploy

30. On-Premise
Lost Time, Lost Opportunities

31. Cloud
Release Cycle
V1 V2 V3 V4 V5 V6 V7 V8 V9 V10

32. Release Cycle
V1 V2 V3 V4 V5 V6 V7 V8 V9 V10
On Premise vs Cloud
V1 V2 V3 V4 V5 V6 V7

33. Release
Test
Build
Cloud

34. Cloud
Build: Development Environments
Image: https://www.flickr.com/photos/kalimistuk/5222488195/in/set-72157594487294945

35. Cloud
Build: Version Control

39. Cloud
Build: Continuous Integration

40. Release
Test
Build
Cloud

41. Cloud
Test: Staging Environments
Image: https://www.flickr.com/photos/kalimistuk/5222488195/in/set-72157594487294945

42. Release
Test
Build
Cloud

43. Cloud
Release: Packaging

44. Cloud
Release: Pre-Release Testing

45. Cloud
Release: Deploy

46. Cloud
Release: Deploy

47. Cloud
Release: The Golden Image

48. + boto: A Python Interface to
Amazon Web Services

49. V1 V2 V3 V2 V3 V4 V5 V6 V5 V6 V7 V8 V7 V8
Cloud
Releasing MindTouch
V3 Rolled
Back
Release +
Same Day Hot Fix
OMG Hot Fix Broke
Something Else, Just
Roll Back To V7
V6 Rolled
Back

50. Release
Test
Build
Enlightenment

51. Enlightenment
Build: Development Environments

52. +

53. Enlightenment
Build: Continuous Integration

54. ++

55. ++
Close ticket associated
with pull request

56. Release
Test
Build
Enlightenment

57. Enlightenment
Test: Automation

58. Enlightenment
Test: Behavior Driven Specifications

59. +

60. Feature: User Login
In order to contribute to MindTouch
As an anonymous user
I need to be able to log in to MindTouch
Background:
Given I am on the homepage
Scenario: Log in to MindTouch via Quick Login widget
When I follow "Sign In"
Then I should see a "#quick-login" element
When I fill in "username" with {{username}}
And I fill in "password" with {{password}}
And I click on the element "form#quick-login .btn"
Then I should be logged in
Scenario: Log in to MindTouch via User Login page
When I go to "/UserLogin"
Then I should be on "/UserLogin"
When I fill in "text-username" with {{username}}
And I fill in "password-password" with {{password}}
And I press "login"
Then I should be logged in

61. Enlightenment
Test: Staging Environments

62. + boto: A Python Interface to
Amazon Web Services

63. Enlightenment
Test: Provide Automated Testing Feedback To Developers

70. Release
Test
Build
Enlightenment

71. Enlightenment
Release: What’s Left?

74. Enlightenment
Everyone Has Bought Into Continuous Delivery
(Even If They Don’t Know It)

75. Image: https://www.flickr.com/photos/29844928@N07/4368522936/

77. Enlightenment
The DevOps Engineer Who Wasn’t There

79. Release
Test
Build

81. What’s Next?

82. The End. Q?

83. Watch the video with slide synchronization on
InfoQ.com!
http://www.infoq.com/presentations/cd-case-
study