Continuous Delivery for people who do not write code - Matthew Skelton - Conflux
4 likes1,176 views
The document discusses continuous delivery (CD) as a set of practices to ensure reliable software releases through automation in build, testing, and deployment. It emphasizes the importance of rapid feedback, small changes, and cross-functional teams that can deploy independently. Key principles include automated testing, monitoring, and the integration of operational features to improve software quality and reduce risks.
Continuous Delivery for people who do not write code - Matthew Skelton - Conflux
- 1. Continuous Delivery for people who do not write code Matthew Skelton, Head of Consulting, Conflux confluxdigital.net / @ConfluxHQ Leeds, 24 Sept 2018
- 2. 2
- 3. Continuously Delivering CD since 2012 Matthew Skelton, Conflux @matthewpskelton matthewskelton.net Leeds, UK 3 2012 2014 2015 2016
- 4. Continuous Delivery Learning Zones 4 learn.londoncd.org.uk learn.pipelineconf.info Over 150 talks on Continuous Delivery from practitioners around the world
- 5. What is Continuous Delivery? 5
- 6. 6
- 7. 7
- 8. Continuous Delivery âReliable Software Releases Through Build, Test, and Deployment Automationâ A specific set of practices and disciplines, tried and tested in many different sectors & contexts worldwide since 2010.
- 9. Continuous Delivery for all Applies to all kinds of software: â Mobile â Embedded â Web â ... From Continuous Delivery with Windows & .NET, OâReilly, 2016, cdwithwindows.net
- 11. 11 speed safety
- 12. We need Speed and Safety Modern software systems are too complicated for manual inspection and assessment We need automated checks for almost every aspect of the software system Use pervasive tooling to detect problems early
- 14. Small changes are less risky Large batches of changes are almost guaranteed to have errors or problems Small batches are easier to reason about, easier to diagnose, easier to change 14
- 15. Agile â Continuous Delivery 15 Jez Humble, continuousdelivery.com
- 16. Agile â Continuous Delivery Automated testing of all aspects of a feature or story as soon as it has been written: â Behaviour â Operational â Security â ... The ability to release a feature or story as soon as it is ready. 16
- 17. CD practices for all areas 17
- 18. CD practices for all areas Business/Workstream applications & services Core supporting products Auxiliary tooling: build & deployment, monitoring Infrastructure (Kubernetes, environments, etc.) 18
- 20. CD Key Principles Rapid feedback on every change Code is always releasable: no big manual testing Deployment Pipeline is the only âroute to liveâ Decoupled, independently releasable units Cross-functional team empowered to deploy live 20
- 21. Real example - 2013 Use visibility to increase trust â speed & safety 21
- 22. Short, wide pipelines â â Shortest (responsible) path to live Long wait for complicated testing https://continuousdelivery.com/2010/09/deployment-pipeline-anti-patterns/ 22
- 23. Testing in Continuous Delivery 95% of testing is automated Operational features tested automatically Most testers sit within Service/Product teams Some testers act as SMEs for test approach Exploratory Testing - specific, manual discipline 23
- 24. Deployment in CD Deployment steps fully automated Deploy during the day - with people around Tracked using an orchestration tool (pipeline) Rollbacks (if possible) or rapid roll-forward 24
- 25. Metrics and logging in CD Service/Product teams see live metrics and logs âFeel the humâ of running systems Metrics and logging for: Services/Products Build / Deployment / Test infrastructure 25
- 26. What does Continuous Delivery feel like? 26
- 28. High-fidelity information Near real-time feedback on changes Instant visibility of the flow of change Rapid drill-down for diagnostics Rapid requirements trace-back for changes 28
- 29. 29 No waiting for a release train
- 30. No waiting for a release train Independent routes to Production Each worksteam moves at its own speed Interdependencies handled by disciplined engineering practices (including versioning, backwards-compatibility, testing techniques) 30
- 31. 31 Heavy lifting done by tooling
- 32. Heavy lifting done by tooling No need for manual inspection of change quality No manual progressing of change sets No âworryingâ whether software will work More time to focus on more valuable things 32
- 34. Reliable releases Reliable tests Reliable deployments Reliable rollbacks Reliable monitoring, logging, metrics 34
- 35. How do activities change with Continuous Delivery? 35
- 36. Agile â Continuous Delivery 36 Jez Humble, continuousdelivery.com
- 37. 37 Early & continuous expertise
- 38. Early & continuous expertise Bring expertise from Release Management / Change Management / Testing / Operations into software dev teams on an ongoing, daily basis The âwise Yodaâ for the âyoung Jediâ teams Enable flow of change 38
- 40. Assess progress regularly Automated code checks across multiple dimensions Regular checks of engineering practices Track delivery metrics: Cycle Time, Deployment Frequency, mean time to restore service (MTTR) 40
- 41. How do we get to Continuous Delivery? 41
- 42. 42 Many parallel routes to live
- 43. Many parallel routes to live Each family of applications and services has its own route to live Rigorous testing with stubs, fakes, proxies Rapid detection of problems and rapid restore of previous good version 43
- 45. Continuous operability Work on operational features ~30% of effort every week, every month Operational aspects tested using automated tests in a deployment pipeline Availability is the #1 feature 45
- 48. Continual small steps There is no sudden âswitch to CDâ Incremental improvements over many months Track using metrics, especially cycle time 48
- 50. Continuous Delivery Small, focused changes with rapid feedback High-fidelity information on changes via tools Early and continuous expertise from Testing, Release Mgt, Change Mgt, Operations Focus on operability to reduce the unexpected 50
- 51. Further reading 51 Continuous Delivery checklist http://cdchecklist.info/ Continuous Delivery with Windows & .NET http://cdwithwindows.net/ Continuous Delivery Learning Zones https://learn.pipelineconf.info/ https://learn.londoncd.org.uk/