Continuous Delivery
Download as PPTX, PDF1 like1,017 views
Continuous delivery is an agile methodology that aims to reduce the cost, time, and risk of delivering software by frequently releasing small, incremental changes. The key goals are to continuously build the right features, reduce lead time, reduce costs through optimization and automation, and reduce risk through resilience and small increments. Continuous delivery utilizes a deployment pipeline to fully automate building, deploying, testing and releasing software. This allows organizations to reliably deliver changes involving a single line of code. It also reduces risk by failing fast and treating every version as a release candidate. Continuous delivery challenges teams to avoid anti-patterns like code freezes, manual processes, and exceptions to the pipeline for releases.
Continuous Delivery
- 1. Continuous Delivery Helping your business win by bringing the pain forward
- 2. Agenda • Introduction • Deployment pipeline • User disruption • Anti-patterns • Adoption • Tools • Conclusion • Q&A
- 3. Introduction
- 4. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Agile Manifesto
- 5. What is continuous delivery? Agile methodology for reducing the cost, time and risk of delivering incremental changes to users.
- 6. Inspired by Lean Startup
- 7. Deliver the right thing. Frequently.
- 8. «You can’t just ask customers what they want and then try to give that to them. By the time you get it built, they’ll want something new.»
- 9. So how frequently? Deliver fast-enough so that a customer didn’t have time to change their mind.
- 10. Goals Continuously: - Build the right thing (MVP, eliminate waste) - Reduce lead time (reduce WiP, eliminate bottlenecks) - Reduce cost (optimize, automate) - Reduce risk (resilience built-in, small increments)
- 11. Who does continuous delivery?
- 12. Let’s rock.
- 13. Redefine «Done» Coded Reviewed Checked-in Built Tested Demoed Released to end-user.
- 14. Determine cycle time 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? Mary & Tom Poppendieck Implementing Lean Software Development
- 15. Reduce risk of release « If it hurts, do it more frequently »
- 16. How?
- 17. By implementing end-to-end automation of build, deploy, test and release processes.
- 19. A pull system spanning full product cycle. - Fully automated (with push button approvals) - Visible - Measurable - Parallelizable
- 21. Build only once.
- 22. Deploy the same way to every environment.
- 23. Fail fast.
- 26. Keep code always releasable.
- 27. Treat every version is a release candidate. Contradicts with traditional approaches.
- 28. Quality goes up. People care.
- 29. Version everything. Single version. No major/minor/patch increments.
- 30. Version control everything. Code, Configuration, Infrastructure…
- 33. Measure.
- 34. Avoid «Big Bang» releases - Small increments - Deploy components independently - Leave backward compatibility
- 35. Avoid branches - True Continuous Integration - work only in mainline - No feature branches - No release branches
- 36. «Feature branching is a poor man’s modular architecture» Dan Bodart Build a modular platform of micro-services.
- 37. Make no exceptions Even urgent production fix should pass the same deployment pipeline.
- 38. User disruption
- 39. 0 downtime deployments
- 40. Blue - Green deployment
- 41. Deployment is not a Release. Release is a marketing decision.
- 42. Smoke test deployment. Release only after that.
- 43. Feature Toggles
- 44. Branch by Abstraction Multiple versions in a single code base.
- 45. Backward compatibility is a key. State is pain in the ass, but remediable with redundancy
- 46. Canary releasing Release to a subset of users.
- 47. Anti-Patterns
- 49. Deployment rarely / late Avoid late contact with reality.
- 54. Manual deployments Sleep well. Forget 2.00 AM deployments.
- 55. Hard to track
- 56. Adoption
- 57. Forget special «Continuous Delivery» projects
- 58. Embrace change trepidation | trep·i·da·tion noun 1 a feeling of fear or agitation about something that may happen: the men set off in fear and trepidation. 2 trembling motion.
- 59. Raise confidence that Change can be safe enough.
- 60. Do not be afraid to fail. Learn what doesn’t work first, then see how to make it better.
- 61. Continuously improve Kaizen | 改善 Japanese for "improvement", or "change for the better" Refers to philosophy or practices that focus upon continuous improvement of processes in manufacturing, engineering, and business management.
- 62. Find the right team and start kicking ass.
- 63. Tools
- 64. Versioning
- 65. Build & dependency management
- 66. CI + Pipelining
- 67. Automation Infrastructure Script streamlining Glu Capistrano DB migrations
- 68. ATDD + Living documentation
- 69. Monitoring
- 70. Micro-services?
- 71. Conclusion
- 72. Continuous Delivery challenges your engineering skills. Are you ready to accept the challenge?
- 73. Thank you!
Editor's Notes
- #10: When business come to you and say you’re releasing too frequently – you’re on the right way.
- #11: Short Lead time fasterFeedbackIncreases motivation, as you get things done faster, less stress
- #15: Большинство– тормозы. Неэффективность процесса и ОПАСНОСТЬ.
- #18: The most complex task is push button.
- #29: Create environment where people get responsible for consequence of their action and they will care (DevOpsphylosophy)
- #30: - Modules / services / entities / staticcontent
- #36: Whybranches? Parallelization. Multipleversionsoftheapp.Unability to keepapplicationstableduringdevelopment.Onegoal, extracare. No merges. Oneversion, pushupteamsforsynchronizationBringspainforward, raisesprofessionalismIsolationillusion
- #37: If people have to use feature branch, something is wrong with your architecture.
- #60: 3WReduce TTD (Time to detect), TTR (Time to recover)
- #62: Practice makes perfect. Toyota way.
- #73: CD is hard. Process flaws become visible.