This document discusses principles of Continuous Delivery (CD) and DevOps. It defines CD, Continuous Integration, and Continuous Deployment. The goal of CD is to have software ready for release at any time by building and testing it frequently. CD relies on principles like keeping everything in version control, automating processes, and having all team members share responsibility for software delivery. CD is enabled by practices like uniform build pipelines, test automation, and deploying changes frequently through production-like environments. CD requires a cultural shift and collaboration between development and operations.

1. bertjan@openvalue.nl
Better software, faster.
Principles of Continuous Delivery and DevOps
Bert Jan Schrijver
@bjschrijver

2. Software delivery in the old days…

3. Bert Jan Schrijver
L e t ’ s m e e t
@bjschrijver

4. Principles
& ingredients of CD
CD vs DevOps
The goal of
Continuous Delivery
Definitions
Where do I start?
CD patterns &
anti-patterns
Conclusion
Outline
W h a t ‘ s n e x t ?
Why should I do CD?
@bjschrijver

5. Definitions
Every change goes through the
build/test pipeline and
automatically gets put into
production.
Continuous Deployment
?!
DevOps
Building and testing software in
such a way that the software can be
released to production at any time.
"Ship early, ship often, sacrificing
features, never quality" - Kyle Neath
Continuous Delivery
Team members integrate their
work frequently. Commits are
verified by automated builds
and tests.
Continuous Integration
Who’s who in CI & CD
@bjschrijver

6. Source: https://i.ytimg.com/vi/64BOxYpVZpU/maxresdefault.jpg
YOU KEEP USING THAT WORD
I DO NOT THINK IT MEANS WHAT YOU THINK IT MEANS

7. Definitions
Every change goes through the
build/test pipeline and
automatically gets put into
production.
Continuous Deployment
Development and operations
engineers being responsible
together for the entire product
lifecycle.
DevOps
Building and testing software in
such a way that the software can be
released to production at any time.
"Ship early, ship often, sacrificing
features, never quality" - Kyle Neath
Continuous Delivery
Continuous Integration
Who’s who in CI & CD
@bjschrijver
Team members integrate their
work frequently. Commits are
verified by automated builds
and tests.

8. How it all started…

10. What is the goal of CD?

11. a repeatable, reliable process
for releasing software
What is the goal of CD?

12. Principles
of Continuous Delivery
@bjschrijver
Build quality in
Keep everything in version control
Continuous improvement
Automate (almost) everything
Everybody is responsible
for the delivery process
Done means released
If it hurts, do it more often

13. Ingredients of Continuous Delivery

14. Ingredients
03
Build & deploy
Information & reporting
05
Design & architecture
02
Culture & organisation
01
Test & verification
04
of Continuous Delivery
@bjschrijver

15. • Agile software development
• Building the right thing
• Building the thing right
• You build it, you run it
• Cross functional teams
• Room to experiment, room for failure
Culture & organisation

16. • Version control
• Branching strategy
• Database changes
• Design for failure
• Feature toggles
• Automated provisioning
Design & architecture

17. • Pipeline:
An automated sequence of stages to deliver software
from version control to your users.
• Build pipeline
• Deployment pipeline
Build & deploy

18. • Testing strategy
• Test automation
• Non functional requirements
• Security
• Performance
• Verify expected business value
Test & verification
NFR’s: requirements that, when not met, make the system non-functional.

19. • Static code analysis
• Traceable pipelines
• Automatic change logs
• Usage metrics
• Dynamic dashboards
• Data driven decisions, act on metrics
• Fix problems before the users notice
Information & reporting

20. WORKED FINE IN DEV
OPS PROBLEM NOW
Continuous Delivery vs. DevOps

21. DevOps: a definition
Development and operations engineers
being responsible together
for the entire lifecycle of a product.

22. :
building and running better-quality software
more quickly and more reliably.
Developers and other IT professionals
working together on a shared goal
DevOps: another definition

23. Why DevOps?
as an enabler for Continuous Delivery, faster problem
resolution and focus on value instead of problems.
DevOps makes your business move faster

24. What is DevOps really about?

25. DevOps is about culture
Source: http://www.azmc.org/wp-content/uploads/2012/11/Arts-and-Culture-Large.jpg

26. DevOps is about freedom and responsibility
Source: https://images.unsplash.com/photo-1449177009399-be6867ef0505

27. DevOps is about empathy
Source: http://www.scarymommy.com/wp-content/uploads/2014/06/empathy.jpg

28. Continuous Delivery sounds great,
but it won’t work here
“
”
Photo: Dave Lehl, text source: Jez Humble

29. “Continuous Delivery won’t work here”
• Stated reasons:
• we’re regulated
• we’re not building
websites
• too much legacy
• our people are too
stupid
• Actual reasons:
• our culture stinks
• our architecture
stinks

30. Why should I do all this?

31. Why CD & DevOps?
• Reducing errors
• Lowering stress
• Empowering teams
• Deployment flexibility
• Practice makes perfect

32. Source: https://7216-presscdn-0-76-pagely.netdna-ssl.com/wp-content/uploads/2011/12/confused-man-single-good-men.jpg
Where do I get started?

33. …said no product manager ever.
J. Paul Reed
Let’s spend the next few months..
..working on automated testing and build/release
infrastructure, and redesigning how our application is
written. We can postpone our feature development.
“
”

34. Take one thing you’re pretty
sure you can improve.
Start small
Tackle the next issue
and keep improving!
Iterate
Approach
How to spark change
When done, share the results
with your team.
Celebrate!
Show results
@bjschrijver

35. CD patterns & anti-patterns

36. Continuous Delivery without DevOps
Anti-pattern
Pattern or anti-pattern?

37. Uniform build pipelines
Anti-pattern
Pattern
Pattern or anti-pattern?

38. Long-running pipelines
Anti-pattern
Pattern or anti-pattern?

39. Obsess on test automation
Pattern
Pattern or anti-pattern?

40. Logging and metrics for ops only
Anti-pattern
Pattern or anti-pattern?

41. Obsess on feedback loops
Pattern
Pattern or anti-pattern?

42. Manual steps in a delivery pipeline
Anti-pattern
Pattern
Pattern or anti-pattern?

43. Long living branches
Anti-pattern
Pattern or anti-pattern?

44. Roll-forward only deployments
Pattern
Pattern or anti-pattern?

45. Put everything in version control
Pattern
Pattern or anti-pattern?

46. Lots of small releases
Pattern
Pattern or anti-pattern?

47. TDD is for software, not infrastructure
Anti-pattern
Pattern or anti-pattern?

48. Dev/prod parity
Pattern
Pattern or anti-pattern?

49. Design for failure
Pattern
Pattern or anti-pattern?

50. Tests don’t provide business value
Anti-pattern
Pattern or anti-pattern?

51. Parallelised pipelines
Pattern
Pattern or anti-pattern?

52. Continuous Delivery =
Continuous Deployment
Anti-pattern
Pattern or anti-pattern?

53. Separate deployment from release
Pattern
Pattern or anti-pattern?

54. Automate database changes
Pattern
Pattern or anti-pattern?

55. Testing NFR’s in the build pipeline
Pattern
Pattern or anti-pattern?

56. Summary

57. What is the goal of a software team?

58. Working, useful software,
in production.

59. Source: https://cdn2.vox-cdn.com/thumbor/J9OqPYS7FgI9fjGhnF7AFh8foVY=/148x0:1768x1080/1280x854/cdn0.vox-cdn.com/uploads/chorus_image/image/46147742/cute-success-kid-1920x1080.0.0.jpg
THAT’S IT.
NOW GO KICK SOME ASS!

60. Questions?
@bjschrijver

61. Thanks for your time.
Got feedback? Tweet it!
All pictures belong
to their respective
authors
@bjschrijver