Continuous Delivery

Automated testing and releasing of software.
Contributed by

Toni Syvänen

Johan Bonneau

Edited by
Published September 04, 2018
Collection
1

What Is Continuous Delivery?

Continuous Delivery (CD) is an engineering practice where each change could be a potential release ready for production. This practice builds on top of the Continuous Integration practice as its starting point and adds to the end a step that releases artifacts for anyone to use. These artifacts could be software packages, container images or virtual machine images.

Why Do Continuous Delivery?

  • Automation reduces the manual work required to do the release, such as publishing the artifact to required locations for deployment and releasing of change notes that can now be taken from version control commit messages.
  • Faster feedback cycles from customers as each change to software can be deployed to production.
  • Happier operations as released software is tested to be ready for production deployment.
  • Readiness to do push button deployments. This can also be taken to the next level which is Continuous Deployment.

How to do Continuous Delivery?

This practice typically requires automation that is run on a server such as Jenkins or Tekton.

Look at Continuous Delivery

Links we love

Check out these great links which can help you dive a little deeper into running the Continuous Delivery practice with your team, customers or stakeholders.

Ask Us Anything


Open Practice Library Logo
Open Practice Library

powered by

Open Innovation Labs Logo
Connect with our Community:
Except where noted, content on this site is licensed under a Creative Commons Attribution 4.0 International license.