Continuous integration, continuous delivery, and continuous deployment are key software delivery processes in a DevOps environment. But what does each one do for your product development and release cycles? Brent Laster explains what these terms really boil down to, and how they work separately and together to help your team release software.
This powerful set of disciplines, best practices, and technologies automates the process of integrating and delivering source code changes from inception through production. Although their implementation may vary, these processes are necessary to ensure that software is released frequently, reliably, and with high quality.
You’ll learn how:
- Continuous integration ensures that individual code changes are suitable for inclusion in the code base and merged in successfully
- Continuous delivery assembles your product, automatically testing the quality and functionality along the way, and produces deliverables that are proven to be deployable
- Continuous deployment simplifies releasing the product to customers, whether it’s in the cloud, via download, or in some other format, while also allowing for limited deployments or rolling deployments back
Table of contents
- Continuous Integration Versus Continuous Delivery Versus Continuous Deployment
- Title: Continuous Integration vs. Continuous Delivery vs. Continuous Deployment
- Release date: November 2017
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781492028901
You might also like
Kubernetes Best Practices
In this practical guide, four Kubernetes professionals with deep experience in distributed systems, enterprise application development, …
Data Science from Scratch, 2nd Edition
To really learn data science, you should not only master the tools—data science libraries, frameworks, modules, …
51+ hours of video instruction. Overview The professional programmer’s Deitel® video guide to Python development with …
What Is the Cloud?
Why are so many companies moving to the cloud? In a word, agility. Businesses need to …