What is continuous delivery?
Continuous delivery (CD) is a software engineering practice where every code change passes through an automated pipeline of build, test, and staging steps so that it is always in a deployable state. The goal is to make releases boring: instead of a high-risk, all-hands deployment event every few weeks, teams can ship small increments to production at any time with confidence that the automated checks have already caught regressions. Continuous delivery extends continuous integration (CI) by ensuring that not only is the code integrated and tested, but it is also packaged and ready for deployment.
Why continuous delivery matters
Large, infrequent releases are risky. When dozens of changes ship together, diagnosing which one caused a production issue becomes a detective exercise. Continuous delivery shrinks the blast radius: each release contains fewer changes, making bugs easier to isolate and roll back. This directly reduces cycle time - the gap between writing code and getting it into users' hands.
CD also creates a faster feedback loop. When a feature reaches production within hours of being merged, the team learns quickly whether it solves the intended problem. This tight loop is central to agile development: you build, ship, measure, and iterate rather than speculating about what users want for months before releasing anything.
Adopting continuous delivery requires investment in automated testing, infrastructure-as-code, and a culture that treats deployment as a routine event rather than a ceremony. Teams that practice CD typically measure lead time (commit to production) and deployment frequency as key health metrics.
How Flux supports continuous delivery workflows
Flux is a project management tool, not a CI/CD pipeline, but it integrates well with continuous delivery workflows. A common pattern is to use board columns that mirror the delivery pipeline: To Do, In Progress, In Review, Staging, and Deployed. As code moves through the pipeline, the corresponding card moves through the board - either manually or automated via Flux's REST API. This gives product managers and non-engineers visibility into the delivery pipeline without needing access to the CI system.
The event-sourced activity log records when each card reaches the Done/Deployed column, providing a deployment history alongside feature context. For teams that label cards by release or version, the multi-board view aggregates deployment status across services, making it easy to see which features shipped in each cycle.
Related terms
See also: Workflow, Cycle time, Agile.