Continuous delivery a happier, safer alternative to release trains
•
4 likes•3,836 views
This document discusses principles and practices for continuous delivery including automating the build, deployment, testing and release process. It emphasizes reducing risk through techniques like feature toggles, blue-green deployments, canary releasing and implementing a production immune system. It also stresses the importance of collaboration between developers, testers and operations personnel.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Continuous delivery a happier, safer alternative to release trains
Similar to Continuous delivery a happier, safer alternative to release trains (20)
More from Thoughtworks
More from Thoughtworks (20)
Recently uploaded
Recently uploaded (20)
Continuous delivery a happier, safer alternative to release trains
- 1. continuous delivery @jezhumble Berlin, 4 october 2012 http://thoughtworks-studios.com/ Tuesday, October 9, 12
- 2. agile 101 "Agile" team Analysis + Design Centralized QA IT Operations Development Integration + QA Release and operation Testing + Showcase Customer Iteration Tuesday, October 9, 12 0 1 2 3 4 The "last mile"
- 4. releasing frequently 1. build the right thing Customer development Agile product development Eric Ries, “The Lean Startup” http://bit.ly/8ZoX5F Tuesday, October 9, 12
- 5. innovate You can't just ask customers what they want and then try to give that to them. By the time you get it built, they'll want something new. Steve Jobs Tuesday, October 9, 12
- 6. scientific method Ideas create hypothesis deliver minimum viable product get feedback (repeat) Tuesday, October 9, 12 Learn Build Code Data Measure Eric Ries, “The Lean Startup” http://bit.ly/8ZoX5F
- 7. ask this question “How long would it take your organization to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis?” Mary and Tom Poppendieck, Implementing Lean Software Development, p59. Tuesday, October 9, 12
- 8. releasing frequently 1. build the right thing 2. reduce risk of release John Allspaw: “Ops Metametrics” http://slidesha.re/dsSZIr Tuesday, October 9, 12
- 9. optimize for mtrs Tuesday, October 9, 12
- 10. optimize for mtrs MTBF MTRS John Allspaw: “Building Resilience in Web Development and Operations” http://www.usievents.com/en/conferences/8-paris-usi-2011/sessions/968-john-allspaw Tuesday, October 9, 12
- 11. releasing frequently 1. build the right thing 2. reduce risk of release 3. real project progress Tuesday, October 9, 12
- 12. agile manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software Tuesday, October 9, 12
- 13. production-ready software Fast, automated feedback on the production readiness of your applications every time there is a change - to code, infrastructure, or configuration Tuesday, October 9, 12
- 14. continuous delivery Software always production ready Releases tied to business needs, not operational constraints Tuesday, October 9, 12
- 15. continuous delivery automation patterns and practices collaboration Tuesday, October 9, 12
- 16. ingredients configuration management continuous integration automated testing Tuesday, October 9, 12
- 17. Develop Local Workstation Mainline Server Build pull Build Build push Tuesday, October 9, 12 ✔ Done!
- 18. Develop Local Workstation Mainline Server Everyone Commits Build To the pull Mainline Build Every Day Build push Tuesday, October 9, 12 ✔ Done!
- 19. build quality in “Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the first place” W. Edwards Deming Tuesday, October 9, 12
- 20. different kinds of testing Business facing Functional acceptance tests Showcases Usability testing Exploratory testing Unit tests Integration tests System tests Non-functional acceptance tests (performance, scaling, ...) AUTOMATED Support programming MANUAL MANUAL / AUTOMATED Critique project AUTOMATED Technology facing Diagram invented by Brian Marick Tuesday, October 9, 12
- 21. deployment pipeline an automated implementation of your system’s build, deploy, test, release process visibility feedback control Tuesday, October 9, 12
- 22. deployment pipeline Delivery team Version control Check in Build & unit tests Automated acceptance tests User acceptance tests Trigger Feedback Check in Trigger Trigger Feedback Feedback Check in Trigger Feedback Trigger Feedback Approval Feedback Tuesday, October 9, 12 Approval Release
- 23. deployment pipeline Tuesday, October 9, 12
- 24. deployment pipeline Tuesday, October 9, 12
- 25. reducing release risk automate provisioning and deployment ensure devs, testers and ops collaborate throughout Tuesday, October 9, 12
- 26. reducing release risk devops incrementalism decoupling deployment and release Tuesday, October 9, 12
- 28. feature toggles blue-green deployments canary releases low risk releases are incremental dark launching production immune system Tuesday, October 9, 12
- 29. DEPENDENT SERVICE 1.0 1.1 Database Abstraction layer Abstraction layer STATIC CONTENT /static/1.1 APPLICATION /static/1.0 Router / Load balancer Interwebs Tuesday, October 9, 12
- 31. router web server Tuesday, October 9, 12 app server DB server
- 33. v1.1 Tuesday, October 9, 12 v1.1 v1.2 v1.2 v1.2 web server router v1.1 app server DB server
- 34. v1.1 Tuesday, October 9, 12 v1.1 v1.2 v1.2 v1.2 web server router v1.1 app server DB server
- 35. Canary Releasing Tuesday, October 9, 12
- 36. Tuesday, October 9, 12
- 37. Tuesday, October 9, 12
- 38. canary releasing Reduce risk of release Multi-variant testing Performance testing Tuesday, October 9, 12
- 39. immune system what if someone replaced your “buy” button with spacer.gif? T cells http://www.flickr.com/photos/gehealthcare/3326186490/ Tuesday, October 9, 12
- 40. release != deployment Tuesday, October 9, 12
- 41. feature toggles Config File [featureToggles] wobblyFoobars: true flightyForkHandles: false some.php <?if ($wobblyFoobars) {?> ... various UI elements <?}?> other.php $fork_handle = ($featureConfig->isOn(‘flightlyForkHandles)) ? new flightyForkHander(aCandle) : new forkHandler(aCandle); Stolen from Martin Fowler http://martinfowler.com/bliki/FeatureToggle.html Tuesday, October 9, 12
- 42. Dark Launching Tuesday, October 9, 12
- 43. Tuesday, October 9, 12
- 44. Tuesday, October 9, 12
- 45. enterprise governance risk management SOX, ITIL, COBIT segregation of duties change management auditing and compliance Tuesday, October 9, 12
- 46. people are the key Get everyone together at the beginning Keep meeting Make it easy for everyone to see what’s happening Continuous improvement (kaizen) Tuesday, October 9, 12
- 47. questions @jezhumble | jez@thoughtworks.com http://continuousdelivery.com/ ThoughtWorks is hiring! http://jobs.thoughtworks.com/ Australia | Brazil | Canada | China Germany | India | Singapore | South Africa Uganda | UK | USA © 2012 ThoughtWorks, Inc. http://thoughtworks-studios.com/ Tuesday, October 9, 12