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.
Overviews of Continuous Deployment and Benefits
Gartner Magic Quadrant: Application Release Automation
-
![]()
Webinar: Learn about Urban Science's journey to "Automating Everything" on their path to Continuous Deployment and Delivery
This talk was given at the 2014 DevOps Enterprise Summit (#DOES14) Urban Science is a business-solutions company focused on supporting the needs of the sales and marketing function of the automotive industry. Urban Science's solution delivery challenges stems from having dozens of products branched dozens of times.
-
![]()
Detailed reference card on Continuous Delivery patterns and anti-patterns with sections on deployment automation and the deployment pipeline
Minimize the time it takes to go from idea to usable software. Learn to use agile techniques and automae the entire software delivery system: build, deploy, test, release.
-
![]()
Slide Deck: Introducing the Continuous Deployment concept with background about testing monitoring tools and culture requirements
Introducing the Continuous Deployment concept with background about testing, monitoring, tools and culture requirements.
-
![]()
Continuous Deployment Best Practices
-
![]()
Blue-Green Deployment - How to Achieve Zero Down-Time Deployment
These days our customers expect their applications to be up and running all the time and literally experience no down-time at all ever. At the same time we should be able to add new features to the existing application or fix existing defects. Is that even possible? Yes, it is, but it is not for free. We have to make a certain effort to achieve what is called zero-downtime deployments.
-
![]()
Elements of a Continuous Deployment Workflow and Strategies
Continuous deployment is an optimal recipe for high productivity in software companies. Read this article to explore what this type of workflow looks like.
-
![]()
-
![]()
-
![]()
-
![]()
-
![]()
blog.snap-ci.com -
![]()
technologyconversations.com -
![]()
martinfowler.com -
![]()
Relation Between Continuous Delivery and Continuous Deployment
-
![]()
Practical continuous deployment - Integration vs. deployment vs. delivery
At Atlassian, we're moving to a continuous delivery and deployment model for all of our business tools, which will allow us to get improvements out to our customers (both internal and external) faster. This post explains the considerations and methodologies behind the move.
-
![]()
-
![]()
-
![]()
-
![]()
-
![]()
-
![]()
-
![]()
Continuous Deployment Case Studies
-
![]()
Continuous Deployment at Instagram
At Instagram, we deploy our backend code 30-50 times a day... whenever engineers commit changes to master... with no human involvement in most cases. This may sound crazy, especially at our scale, but it works really well. This post talks about how we implemented this system and got it working smoothly.
-
![]()
-
![]()
2014technologyconversations.com -
![]()
-
![]()
-
![]()
-
![]()
-
![]()
Continuous Deployment with Specific Tools and Environments
-
![]()
2015azure.microsoft.com -
![]()
-
![]()
-
![]()
-
![]()
mesosphere.com -
![]()
-
![]()
-
![]()
2016azure.microsoft.com -
![]()
-
![]()
-
![]()
-
![]()
-
![]()
-
![]()
codeship.com -
![]()
circleci.com -
![]()
semaphoreci.com
Vendors Offering Continuous Deployment Solutions
-
![]()
electric-cloud.comA single DevOps platform that supports the entire end-to-end software development and delivery process -
![]()
-
![]()
zerostack.comA Continuous Integration and Continuous Deployment Platform for Cloud-Native Applications. -
![]()
appcito.comSupports Continuous Deployment for two main use cases: Blue-green production servers and production traffic copied to test servers. -
![]()
semaphoreci.comEnables your team to roll-in revisions and gain feedback faster by automatically deploying a good version of your code to the desired server. -
![]()
speedcurve.comSpeedCurve's Continuous Deployment dashboard helps you keep the development of your site on track with continuous feedback on your performance pipeline. -
![]()
hub.jazz.netBuild and deploy feature that automates the continuous deployment of your projects. -
![]()
www8.hp.comA continuous deployment solution that provides automation and release management of complex multi-tier applications across the application lifecycle. -
![]()
app.shippable.comThe Shippable continuous deployment platform integrates teams and processes to streamline shipping of software.
Further Reading
Know an online resource which could be relevant for this wiki page? We're constantly updating our wiki and will be happy to review it!
Gartner Magic Quadrant: Application Release Automation
Suggest a Resource!
Subscribe
to be notified of new updates
Enter your email address to subscribe to this wiki and receive notifications of new content being added