Many businesses are adopting Continuous Delivery because the frequent releases and low risk nature of these releases can provide a competitive cost advantage. This is particularly important in a world where many businesses can only exist and survive and are defined by software based systems.
27. Pipeline Summary
• Build a 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
• One Deployment Script for all Environments
• Automate everything – Push one button
• Version Control all configuration
• Environments should match where practical
Start-up
Follow Learn Start-up
We pratitice CD during product development and always looking to get feature into customers hands
Fast feedback – Are we building the right thing?
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?
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
Heartbleed bug – How many of you would feel comfortable fixing it a 5pm on a Friday?
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.
First Principle behind the Agile Manifesto
Agile methods and implementations focus on requirements to development and test, not getting working software to the customer.
The aim of doing releases more frequently
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.
Take a Drink
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
First Principle behind the Agile Manifesto
Agile methods and implementations focus on requirements to development and test, not getting working software to the customer.
A book on Continuous Delivery and DevOps Experience Reports