You are viewing an old version of this page. View the current version.
Continuous Deployment Overview
Continuous Deployment is the practice of continuously pushing to production new versions of software under development. In organizations like Facebook and Amazon, software is deployed thousands of times each day.
Continuous Deployment vs. Continuous Integration (CI) and Continuous Delivery
- Continuous Integration is a software development practice in which you build and unit-test software every time a developer checks in new code.
- Continuous Delivery (CD) is a software development practice in which continuous integration, automated testing, and automated deployment capabilities allow software to be developed and deployed rapidly, reliably and repeatedly with minimal manual overhead.
- Continuous Deployment - Continuous Deployment is a software development practice in which every code change goes through the entire pipeline and is put into production, automatically, resulting in many production deployments every day.
With Continuous Delivery your software is always release-ready, yet the timing of when to push it into production is a business decision, and so the final deployment is a manual step. With Continuous Deployment, any updated working version of the application is automatically pushed to production. Continuous Deployment mandates Continuous Delivery, but the opposite is not required.
Below we have compiled publicly available sources from around the world that present views on Continuous Deployment.
Overviews of Continuous Deployment and Benefits
Continuous Deployment Best Practices
Relation Between Continuous Delivery and Continuous Deployment
Continuous Deployment Case Studies
Continuous Deployment with Specific Tools and Environments
Vendors Offering Continuous Deployment Solutions
- No labels