Continuous Integration vs. Continuous Delivery


Learn how to deliver software that is released frequently, reliably, and with high quality.

LaunchDarkly empowers all teams to deliver and control their software.

©2021 Catamorphic Co

Meetup icon
Linkedin icon
Twitter icon

LaunchDarkly has helped us be significantly more confident and have fewer discussions about the impact of potentially risky code going out.

Jish Chu

Rob Zuber

Director of Engineering, Upserve

Discover how to deploy code with less risk

Get a Demo

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.

  • 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.