Concepts & Practices
8 entriesContinuous delivery keeps every change in a releasable state and automates the path from commit to production-ready, with the release itself a business decision. It adds environments, approvals, promotion and release orchestration on top of continuous integration.
Pipeline & Release Orchestration Platforms
14 entriesModel pipelines, environments, approvals and promotion.
GitOps & Kubernetes Delivery
7 entriesDeclarative delivery driven by Git.
Cloud Delivery Services
4 entriesProvider-managed delivery.
Related Pages
11 entriesNeighbouring pages on this site.
Frequently Asked Questions
What is continuous delivery?
A practice where every change is automatically built, tested and prepared so it can be released to production at any time, with the release triggered by a person or business decision.
What is the difference between continuous delivery and continuous deployment?
In continuous delivery the final push to production is a manual decision; in continuous deployment every change that passes the pipeline is released automatically.
What does a continuous delivery tool do?
It models the pipeline and environments, promotes artifacts between stages, enforces approvals and policies, and records what is deployed where.
Argo CD or Spinnaker?
Argo CD (and Flux) suit Kubernetes-centred teams who want Git as the source of truth; Spinnaker suits multi-cloud delivery with rich deployment strategies; Harness and Octopus suit teams wanting a commercial release platform.
How current is this list?
Links were checked in October 2026. Archived or renamed products are labelled; sites that block automated checks are kept and may need a manual click.