Continuous Delivery

See also Continuous integration

Snippet from Wikipedia: Continuous delivery

Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, following a pipeline through a "production-like environment", without doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.

Continuous delivery contrasts with continuous deployment (also abbreviated CD), a similar approach in which software is also produced in short cycles but through automated deployments even to production rather than requiring a "click of a button" for that last step.: 52 As such, continuous deployment can be viewed as a more complete form of automation than continuous delivery.


The Continuous Delivery Pipeline (also referred to as ‘pipeline’) represents the workflows, activities, and automation needed to provide a continuous release of value to the end user. The pipeline consists of four elements: Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand.

  • Lean Startup Cycle

todo: FIXME

  • AWS CodeDeploy
  • CA Automic
  • CA Nolio
  • Capistrano
  • Deploybot
  • Deployment Manager
  • Disnix
  • ElasticBox
  • ElectricFlow
  • Fastlane
  • Go
  • JuJu
  • NixOps
  • Octopus Deploy
  • Otto
  • Project Kudu
  • Pulumi
  • RapidDeploy
  • Rundeck
  • SmartFrog
  • UrbanCode Deploy
  • XL Deploy
  • webhook
  • method/continuous_delivery.txt
  • Last modified: 2022/08/17 14:55
  • by Henrik Yllemo