Sustainable Continuous Delivery: Patterns for rapid and reliable Releases @ DevOpsCon Berlin
3 likes348 views
The document outlines patterns for sustainable continuous delivery (CD) focusing on reliable and rapid releases. It emphasizes the importance of mapping value streams, measuring key metrics, and designing intelligent pipelines while addressing team dynamics and self-service platforms. Manuel Pais presents a framework for treating delivery pipelines as products to enhance efficiency and sustainability.
Sustainable Continuous Delivery: Patterns for rapid and reliable Releases @ DevOpsCon Berlin
- 1. Sustainable CD - Patterns for Rapid & Reliable Releases 1 Manuel Pais
- 2. About me Manuel Pais MS Software Eng @manupaisable me@manuelpais.net http://manuelpais.net DevOps Consultant & Trainer Co-author of “Team Topologies” Focused on teams and flow 2@manupaisable | manuelpais.net
- 3. @manupaisable | manuelpais.net 3 Today 1. Intro to boring releases 2. Patterns for reliable releases 3. Patterns for rapid releases 4. Patterns for sustainable delivery
- 4. @manupaisable | manuelpais.net 4 Today 1. Intro to boring releases 2. Patterns for reliable releases 3. Patterns for rapid releases 4. Patterns for sustainable delivery
- 9. @manupaisable | manuelpais.net 9 Today 1. Intro to boring releases 2. Patterns for reliable releases 3. Patterns for rapid releases 4. Patterns for sustainable delivery
- 10. “ability to get changes of all types, into production, or into the hands of users, safely and quickly in a sustainable way” –Dave Farley & Jez Humble continuousdelivery.com @manupaisable | manuelpais.net 10
- 11. “ability to get changes of all types, into production, or into the hands of users, safely and quickly in a sustainable way” –Dave Farley & Jez Humble continuousdelivery.com @manupaisable | manuelpais.net 11
- 12. Patterns for reliable releases 12@manupaisable | manuelpais.net
- 14. Patterns for reliable releases 1. Map value stream in the pipeline 14@manupaisable | manuelpais.net
- 17. Patterns for reliable releases 17@manupaisable | manuelpais.net
- 19. Patterns for reliable releases 1. Map your value stream to the pipeline 2. Measure key metrics 19@manupaisable | manuelpais.net
- 20. Speed lead time Quality failure rate Operability MTTR 20@manupaisable | manuelpais.net
- 22. Flow efficiency = “generally flow efficiencies are around the 15% mark” http://leankanban.com/flow-efficiency-a-great-metric-you-probably-arent-using @manupaisable | manuelpais.net 22
- 23. issue is not how long it takes to do something, it's how long we're waiting for it to get done @manupaisable | manuelpais.net 23
- 24. Patterns for reliable releases 24@manupaisable | manuelpais.net
- 26. Patterns for reliable releases 1. Map your value stream to the pipeline 2. Measure key metrics on speed, quality & operability 3. Put in the groundwork 26@manupaisable | manuelpais.net
- 27. Automated build in clean environment Ephemeral prod-like test environment Health checks and fast smoke tests Automated acceptance tests (BDD) Everything as code (one truth) Single path to production 27@manupaisable | manuelpais.net
- 29. Patterns for reliable releases 1. Map value stream in the pipeline 2. Measure key metrics 3. Put in the groundwork 29@manupaisable | manuelpais.net
- 30. @manupaisable | manuelpais.net 30 Today 1. Intro to boring releases 2. Patterns for reliable releases 3. Patterns for rapid releases 4. Patterns for sustainable delivery
- 31. “ability to get changes of all types, into production, or into the hands of users, safely and quickly in a sustainable way” –Dave Farley & Jez Humble continuousdelivery.com @manupaisable | manuelpais.net 31
- 32. @manupaisable | manuelpais.net 32 Build Test Deploy
- 33. @manupaisable | manuelpais.net 33 FixMonitorRun CI Peer review Infra Security Comply Database Accept UX Deploy
- 34. @manupaisable | manuelpais.net 34 can’t auto- scale people How to cope with ever increasing cognitive load on teams to build and run applications?
- 35. Patterns for rapid releases 1. Design intelligent pipelines 2. Evolve teams and interactions 3. Set up a self-service platform 35@manupaisable | manuelpais.net
- 37. Patterns for rapid releases 1. Identify & remove bottlenecks 2. Shorten path to production 3. Continuous pruning 37@manupaisable | manuelpais.net
- 38. Waiting for pipeline @manupaisable | manuelpais.net 38
- 39. Waiting for pipeline @manupaisable | manuelpais.net 39
- 40. Waiting for dependencies @manupaisable | manuelpais.net 40
- 41. Waiting for dependencies @manupaisable | manuelpais.net 41
- 42. Patterns for rapid releases 1. Design intelligent pipelines 2. Evolve teams and interactions 3. Set up a self-service platform 42@manupaisable | manuelpais.net
- 43. Patterns for rapid releases 1. Identify & remove bottlenecks 2. Shorten path to production 3. Continuous pruning 43@manupaisable | manuelpais.net
- 44. Risk-based activities (short & wide pipeline) @manupaisable | manuelpais.net 44
- 45. Patterns for rapid releases pipelines 1. Set up a self-service platform 45@manupaisable | manuelpais.net
- 47. Patterns for rapid releases 1. Identify & remove bottlenecks 2. Shorten path to production 3. Continuous pruning & fast feedback 47@manupaisable | manuelpais.net
- 48. 48 “There are just two moments when an automated test provides useful information: the first time it passes and when it subsequently fails.” @manupaisable | manuelpais.net Continuous pruning
- 52. Patterns for rapid releases pipelines Bonus! Evolve teams and interactions 1. Set up a self-service platform 52@manupaisable | manuelpais.net
- 54. Patterns for rapid releases 1. Identify & remove bottlenecks 2. Shorten path to production 3. Continuous pruning & fast feedback 54@manupaisable | manuelpais.net
- 55. @manupaisable | manuelpais.net 55 Today 1. Intro to boring releases 2. Patterns for reliable releases 3. Patterns for rapid releases 4. Patterns for sustainable delivery
- 56. “ability to get changes of all types, into production, or into the hands of users, safely and quickly in a sustainable way” –Dave Farley & Jez Humble continuousdelivery.com @manupaisable | manuelpais.net 56
- 59. •CI tool •CD tool (orchestration) •Plugins / 3rd party tools •Pipeline definitions •Source repos •Artifact repos •CI + CD infrastructure @manupaisable | manuelpais.net 59 Delivery (CI/CD) system
- 60. CI/CD Toolchain Pipelines Infra App 1 App 2 CI/CD tool Artifact tool Artifacts Delivery (CI/CD) system
- 61. System Operability Available (minimal downtime) Scalable (no pipelines waiting to run) Monitored (alerts on resources and errors) Recoverable (focus on diagnosis & MTTR) @manupaisable | manuelpais.net 61
- 62. Patterns for sustainability 1. Treat your pipeline as a product 2. Treat your pipeline as a product 3. Treat your pipeline as a product 62@manupaisable | manuelpais.net
- 63. Immutable infrastructure Blue-green deployments Monitoring & alerting Aggregated logging Pipelines-as-code Auto-scaling 63@manupaisable | manuelpais.net
- 64. About me Manuel Pais MS Software Eng @manupaisable me@manuelpais.net http://manuelpais.net DevOps Consultant Co-author of “Team Topologies” Focused on teams and flow 64@manupaisable | manuelpais.net
- 67. @manupaisable | manuelpais.net 67 https://www.youtube.com/watch?v=MAFpuwB7-to