Continuous Delivery

continuous delivery @jezhumble Berlin, 4 october 2012 http://thoughtworks-studios.com/Tuesday, October 9, 12

agile 101 "Agile" team Analysis + Design Centralized QA IT Operations Development Integration + QA Release and operation Customer Testing + Showcase Iteration 0 1 2 3 4 The "last mile"Tuesday, October 9, 12

social disrupting traditional businesses http://code.flickr.com/Tuesday, October 9, 12

releasing frequently 1. build the right thing Customer development Agile product development Eric Ries, “The Lean Startup” http://bit.ly/8ZoX5FTuesday, October 9, 12

innovate You cant just ask customers what they want and then try to give that to them. By the time you get it built, theyll want something new. Steve JobsTuesday, October 9, 12

scientific method Ideas create hypothesis Learn Build deliver minimum viable product Data Code get feedback Measure (repeat) Eric Ries, “The Lean Startup” http://bit.ly/8ZoX5FTuesday, October 9, 12

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

releasing frequently 1. build the right thing 2. reduce risk of release John Allspaw: “Ops Metametrics” http://slidesha.re/dsSZIrTuesday, October 9, 12

optimize for mtrsTuesday, October 9, 12

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-allspawTuesday, October 9, 12

releasing frequently 1. build the right thing 2. reduce risk of release 3. real project progressTuesday, October 9, 12

agile manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable softwareTuesday, October 9, 12

production-ready software Fast, automated feedback on the production readiness of your applications every time there is a change - to code, infrastructure, or conﬁgurationTuesday, October 9, 12

continuous delivery Software always production ready Releases tied to business needs, not operational constraintsTuesday, October 9, 12

continuous delivery automation patterns and practices collaborationTuesday, October 9, 12

ingredients configuration management continuous integration automated testingTuesday, October 9, 12

Local Develop Workstation Mainline Server Build pull Build Build ✔ Done! pushTuesday, October 9, 12

Local Develop Workstation Everyone Commits Mainline Server Build To the pull Mainline Build Every Day Build ✔ Done! pushTuesday, October 9, 12

build quality in “Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the ﬁrst place” W. Edwards DemingTuesday, October 9, 12

diﬀerent kinds of testing Business facing AUTOMATED MANUAL Showcases Support programming Functional acceptance Usability testing tests Critique project Exploratory testing Unit tests Non-functional Integration tests acceptance tests System tests (performance, scaling, ...) AUTOMATED MANUAL / AUTOMATED Technology facing Diagram invented by Brian MarickTuesday, October 9, 12

deployment pipeline an automated implementation of your system’s build, deploy, test, release process visibility feedback controlTuesday, October 9, 12

deployment pipeline Delivery team Version control Build & unit Automated User acceptance Release tests acceptance tests tests Check in Trigger Feedback Check in Trigger Feedback Trigger Feedback Check in Trigger Feedback Trigger Feedback Approval Feedback ApprovalTuesday, October 9, 12

deployment pipelineTuesday, October 9, 12

reducing release risk automate provisioning and deployment ensure devs, testers and ops collaborate throughoutTuesday, October 9, 12

reducing release risk devops incrementalism decoupling deployment and releaseTuesday, October 9, 12

devops culture automation measurement sharingTuesday, October 9, 12

feature toggles blue-green deployments canary releases low risk releases are incremental dark launching production immune systemTuesday, October 9, 12

DEPENDENT SERVICE 1.0 1.1 Database Abstraction layer Abstraction layer STATIC CONTENT /static/1.1 APPLICATION /static/1.0 Router / Load balancer InterwebsTuesday, October 9, 12

blue-green deploymentsTuesday, October 9, 12

router web app DB server server serverTuesday, October 9, 12

v1.1 v1.1 v1.1 router web app DB server server serverTuesday, October 9, 12

v1.1 v1.1 v1.1 router v1.2 v1.2 v1.2 web app DB server server serverTuesday, October 9, 12

Canary ReleasingTuesday, October 9, 12

Tuesday, October 9, 12

canary releasing Reduce risk of release Multi-variant testing Performance testingTuesday, October 9, 12

immune system what if someone replaced your “buy” button with spacer.gif? T cells http://www.ﬂickr.com/photos/gehealthcare/3326186490/Tuesday, October 9, 12

release != deploymentTuesday, October 9, 12

feature toggles Config File [featureToggles] wobblyFoobars: true some.php flightyForkHandles: false <?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.htmlTuesday, October 9, 12

Dark LaunchingTuesday, October 9, 12

Tuesday, October 9, 12

enterprise governance risk management SOX, ITIL, COBIT segregation of duties change management auditing and complianceTuesday, October 9, 12

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

http://maciejwalkowiak.pl	588
http://www.linkedin.com	9
https://www.rebelmouse.com	1

Continuous Delivery

by Jez Humble

Accessibility

Categories

Upload Details

Usage Rights

3 Embeds 598

Statistics