Continuous Delivery. Jez Humble, ThoughtWorks #continuousdelivery DevOpsDays, Hamburg

Transcription

1 Continuous Delivery Jez Humble, ThoughtWorks #continuousdelivery DevOpsDays, Hamburg

2 Agile 101 "Agile" team Analysis + Design Development Centralized QA Integration + QA IT Operations Release and operation Customer Testing + Showcase Iteration The "last mile"

3 web 2.0 disrupting traditional businesses

4 releasing frequently feedback from users Customer developent Agile product development Eric Ries, The Lean Startup

5 releasing frequently feedback from users reduce risk of release John Allspaw: Ops Metametrics

6 releasing frequently feedback from users reduce risk of release real project progress

7 agile manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

8 production-ready software Fast, automated feedback on the production readiness of your applications every time there is a change - to code, infrastructure, or configuration

9 continuous delivery Customer Delivery team Constant flow of new features into production Software always production ready Releases tied to business needs, not operational constraints

10 enterprise lean startups Business units act as VCs Products, not projects Completely cross-functional teams Works great with many small, distributed teams and RESTful architecture BUT...

11 value stream mapping Product opportunity assessment Product discovery Product planning and estimation Development Final testing and approval Release Value-added time 3 days 1 week 10 days 7 weeks 1 week 2 hours Elapsed time 1 week 10 days 3 days 5 days 2 days

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

13 deployment pipeline

14 deployment pipeline

15 principles create a repeatable, reliable process for releasing software automate almost everything keep everything in version control if it hurts, do it more often, and bring the pain forward build quality in done means released everybody is responsible for delivery continuous improvement

16 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? What gets in the way of getting software out of the door? Mary and Tom Poppendieck, Implementing Lean Software Development, p59.

17 practices only build your binaries once deploy the same way to every environment smoke test your deployments keep your environments similar if anything fails, stop the line

18 continuous integration Professor Plum P1 P2 P3 P4 P4 P1 P2 P3 P4 P5 Mainline G1 P1 B1 B1 P2 G2 P3 B2 B2 G3 P4 P5 G1 B1 P1-2 G2 B2 P3 G3 P4-5 G4 G5 G6 G1 G2 G3 G4 G5 G6 Reverend Green G2 G3 G4 everybody checks in to mainline use branch by abstraction for architectural change use feature bits to switch off incomplete features Diagram invented by Martin Fowler

19 different kinds of testing AUTOMATED Business facing MANUAL Support programming Functional acceptance tests Unit tests Integration tests System tests Showcases Usability testing Exploratory testing Non-functional acceptance tests (performance, scaling,...) Critique project AUTOMATED Technology facing MANUAL / AUTOMATED Diagram invented by Brian Marick

20 canary releasing

21 data migration

22 objections Visibility and control over locking down Compliance - automation over documentation Auditing - see who does what Make it easy to remediate outages

23 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)

24 thank you!