This document discusses continuous delivery practices. It begins by highlighting benefits from reports such as higher IT performance, organizational performance, and throughput/stability. It then discusses concepts like delivering value to customers through early and continuous delivery, reducing risk through small frequent changes, and tracking real progress. The rest of the document details practices like automation, version control, continuous integration, deployment pipelines, and mindsets like being lean and agile. It provides examples of deployment pipelines and automation of testing, infrastructure, and deployments. It emphasizes automating as much as possible and not ignoring data.

1. Continuous
Delivery
InPractice

2. PatricFornasier
MarcHofer
SoftwareEngineer
ThoughtWorks・Springer・Yelp・Swisscom
♥ peopleandbuildingstuff
SoftwareEngineer
Zühlke・ThoughtWorks・effectiveAgile
♥ tolearnfrommistakes

3. Agenda
why?
what?
how?

4. Why?

5. STATE of DevOps report

6. Higher IT
performance
60x failures
168x recovery
30X deploys
200x leadtimes

7. Higher
organisational
performance
2x profitability
marketshare
productivity

8. Higher
throughput &
stability
11.6 secs
amazon-may2011

9. Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software.
‒ Agile Manifesto
“

10. time
plan
spec
design
code
test
deploy
iteration 1 iteration 2iteration ...

11. iteration/
sprint
idea

12. time
fall
plan
spec
test
deploy
SCRUM
ScrumWater

13. When I come in one day and tell you the
project will end in one week, you have to be
ready to package up and deliver what you’ve
got as the final product.
‒ Tom DeMarco
IEEE Software, 2009
“

15. IDEAS
CODEDATA
learn build
measure

16. Reduce
RISK

17. change
time
change
time
big change
= big risk
small change
= small risk

18. Mean
Time
To
Recover
168x

19. TRACK
real
PROGRESS

20. Whatisrealprogress?

21. WHAt?

22. Practices
Automation
VersionControl
ContinuousIntegration

23. Deployment
Pipeline
devtorelease

24. Mindset
lean
agile
devOps

25. HOw?

26. Value
Stream
Mapping

27. PROCESS
A
PROCESS
B
PROCESS
C
PROCESS
D
supplier customer
information flows
material flows

28. PROCESS
A
DEV RELEASE
PROCESS
D
supplier customer
information flows
material flows
continuous deluvery

29. How long would it take your organization to
deploy a change that involved just one single
line of code [...] on a repeatable, reliable
basis?
‒ Mary and Tom Poppendieck
Implementing Lean Software Development, 2006
“

30. Deployment
Pipeline

31. Build
commit
Acc.
Tests
Staging Prod
automatic
promotion gated
verify
store
time

34. time
Build
Acc.
Tests
Staging Prod
component X
Build
Acc.
Tests
component Y
Sys.
Tests

36. http://arojgeorge.ghost.io/

37. time
Build
Acc.
Tests: n
Staging Prod
CDC
Tests
Sys.
Tests
Acc.
Tests: 1
Perf
Tests

38. 70,000 tests
350 runs
700 days
3,000 concurrenttests
200 machines
1.5M dockercontainers

39. time
Build
Acc.
Tests
Staging Prod
Build
Acc.
Tests
Staging Prod
Build
Acc.
Tests
Staging Prod
Build
Acc.
Tests
Staging Prod
Build
Acc.
Tests
Staging Prod#5
#4
#3
#2
#1

40. https://medium.com/continuous-delivery/architecting-for-continuous-delivery-77890e139ef6

41. VERSION
CONTROL
TEST
SYSTEM
CONFIG
build
scripts
APP
CONFIGTOOLSgit
HG
...
DB
SCRIPTSCODE
DEPLOYMENT
SCRIPTS
DEPS
INFRA
CONFIG
DOCS
IDE
CONFIG
ENCRYPTED (!!)
SENSITIVE DATA

42. Continuous
Integration
...ismoreoftenthanyouthink.

43. develop
build
build
pull
push
time

44. time
commit
pull
build

45. build
pull
develop
build
push
pull
build
commit

46. build
pull
develop
build
push
pull
build
commit

47. BUILDAutomation
FAST
GATE TO
COmmit
AGREED
W/TEAM
FEEDBACK
TOOLS
MAKEBAZEL
GRADLERAKE ...
VERSION
CONTROLLED
COMMAND
LINE
SAME ON
CI
COMPILE
TESTS
PACKAGE
CHECKS
...

48. test
automation

49. find bugs prevent bugs
MANUAL TESTS
AUTOMATION
SUITES
UNIT
# tests# tests confidence
FUNCTIONAL
SYS
INTEGRATION
UNIT
confidence

50. time
Unit
tests
int
tests
acc.
tests
trigger
feedback

53. infra &
environment
automation

54. Deployment
automation

55. 1) install and boot new version
2) run health checks
3) route traffic
4) monitor
5) repeat
App B
App C
App A
App A'
routeLOAD
BALANCER/
DNS
inbound
traffic

56. Week 12
Week 1

57. RELEASING

58. Deployment!=Release
…Experiment
…DarkLaunching

59. RECAP

60. don't ignore
the data

61. Automate

62. Automate

63. Auto
mate

64. it's stuff
you do...

65. Thanks
@patforna @mhoefi