Concepts & Practices
6 entriesContinuous deployment releases every change that passes the automated pipeline to production, without a manual gate. It depends on strong automated testing, observability and safe rollout techniques such as canary releases, blue-green deployments and feature flags.
Deployment Automation Tools
13 entriesPush builds to servers, clusters and clouds.
Progressive Delivery & Rollouts
7 entriesRelease gradually and roll back fast.
Feature Flags & Experimentation
7 entriesDecouple deploy from release.
Push-to-Deploy Platforms
7 entriesDeploy from Git with no pipeline to build.
Related Pages
12 entriesNeighbouring pages on this site.
Frequently Asked Questions
What is continuous deployment?
The practice of automatically releasing every change that passes the pipeline to production, without a manual approval step.
Is continuous deployment safe?
It is safe when paired with strong automated tests, monitoring, and progressive rollout with fast rollback; feature flags separate deploying code from exposing it to users.
What is progressive delivery?
Releasing to a small share of traffic first (canary), or switching between two environments (blue-green), and widening the rollout as metrics stay healthy; Argo Rollouts and Flagger automate this on Kubernetes.
Do I need continuous deployment?
Not always. Many teams practise continuous delivery and keep a deliberate release decision; see the Continuous Delivery Tools page.
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.