Downloaded 12 times
Uploaded byAlan Parkinson
What is Continuous Delivery?
Continuous delivery is an effective approach that automates the process of building, testing, and releasing software, ensuring rapid and high-quality deliveries to customers. It emphasizes early customer satisfaction through frequent and low-risk releases, advocating for minimal differences between development environments and streamlined deployment processes. By utilizing automated checks and focusing on small batch sizes, organizations can encourage fast feedback and adapt to changes efficiently.
More Related Content
Similar to What is Continuous Delivery?
What is Continuous Delivery?
- 1. What is ContinuousDelivery? Alan Parkinson @alan_parkinson
- 2. Hindsight Software a leanStart-up
- 3. Fast feedback Are webuilding the right thing?
- 4. Software as a CompetitiveAdvantage
- 5. Creating a featureis an investment Has no return until it is being used
- 6. The Last Mile:Releasing
- 8.
- 9. Are we allAgile?
- 10. our highest priorityis to satisfy the customer through early and continuous delivery of valuable software “ ”
- 11. effective pattern forgetting software from development to release
- 12. if it hurt’s,do it more often
- 13. Low-risk, frequent, cheap,rapid and predictable process
- 14.
- 15. The Deployment Pipeline automatedimplementation of your build, test, deploy, and release process
- 16.
- 17.
- 18. Fail fast andgive feedback
- 19.
- 20. Cycle Time commit torelease
- 22. Pattern 2 -Deployment
- 23. one deployment script torule them all CC Attribution-ShareAlike: mendhak https://flic.kr/p/62WDfS
- 25. minimise the differencesbetween environments
- 26. effective pattern forgetting software from development to release
- 27. Pipeline Summary • Builda installable Binary once • Pass the built binary through quality gates • Trigger the pipeline on every change • Done == Released to Customers • Based on Lean Thinking • Avoid queues in the pipeline • Track cycle time • Business decides when to release
- 28. Deployment Summary • OneDeployment Script for all Environments • Automate everything – Push one button • Version Control all configuration • Environments should match where practical
- 29. Continuous Delivery: Reliable SoftwareReleases Through Build, Test, and Deployment Automation By Jez Humble And Dave Farley
- 30. Build Quality In ContinuousDelivery and DevOps Experience Reports 70% of author royalties to Code Club leanpub.com/buildqualityin @buildqualityin
- 31.
- 32.
- 33. Testing in ContinuousDelivery
- 34.
- 35.
- 36.
- 37.
Editor's Notes
- #3 Start-up Follow Learn Start-up We pratitice CD during product development and always looking to get feature into customers hands
- #4 Fast feedback – Are we building the right thing?
- #6 You see no ROI from a new feature until it’s released to customers What cold of the business have done with the money while it waits?
- #7 Delivering software from Testing to Production is known as the last mile. Teams often batch up several sprints worth of changes all to be deployed at the same time
- #8 Heartbleed bug – How many of you would feel comfortable fixing it a 5pm on a Friday?
- #9 Manual configuration of system takes a long time Many issues found during deployment - People working weekends. - Emergency fixes from Developers and Testers Deployment manual rewritten during deployments for work arounds Staging and Production Environments don’t match Separate Operations team – They are interested in SLA’s and not getting the latest features into production Office of National Statistics can no longer deploy because the system is so brittle.
- #11 First Principle behind the Agile Manifesto Agile methods and implementations focus on requirements to development and test, not getting working software to the customer.
- #14 The aim of doing releases more frequently
- #18 It seems so simple that it couldn’t possibly make that big of difference, but it does. And there is historical precedent for it as well. The principle of working is small batches has proved it’s merit in Agile software development and on an even larger stage during the manufacturing revolutions of the 1970s and 1980s.
- #22 Take a Drink
- #24 One button push deployment Testing, Staging, and Production should all use the same deployment scripts Using the same script means it gets checked every time the pipeline is executed
- #27 First Principle behind the Agile Manifesto Agile methods and implementations focus on requirements to development and test, not getting working software to the customer.
- #31 A book on Continuous Delivery and DevOps Experience Reports
- #32 Take a Drink
- #33 Take a Drink