Continuous Deployment: Moving Past Continuous Delivery
Continuous Delivery is a amazing practice when compared to slower release cycles. But it shouldn't be the end goal. Continuous Deployment, safe automatic deployment of frequent small commits, is the next step. To get to a fully automatic release process the way that your team writes and releases features will need to fundamentally change. The tools, learnings and techniques presented will be widely applicable regardless of how far along adopting continuous practices you are.
Outline/structure of the Session
- Defining Continuous Delivery and Continuous Deployment
- Why Continuous Delivery is a bad place to stop
- Key Continuous Deployment Insights
- Automated release is REALLY important
- Safety First
- Never branch
- Sustained investment in automated testing
- You can go back and fix it
- No one feels ready or safe on day #1
- Predictions for the future
Learn the difference between Continuous Deployment and Continuous Delivery.
Learn about the pitfalls of stopping at Continuous Delivery.
Learn what to do to deploy safer and faster and why.
Engineering, DevOps, QA, Product Managers