Simple definition
Continuous delivery automatically builds and tests deployable software while optionally retaining a manual production approval step.
Purpose and use
Continuous Delivery keeps an application tested and releasable through an automated delivery process.
How does it work?
The pipeline builds, checks and prepares artifacts. A human decision can remain necessary before production release.
Example and verification
Verify that the tested artifact is the one released and that environment-specific configuration is controlled separately.
Points to watch
Continuous delivery differs from continuous deployment: automating the final production release is not required by the former.
In short
Release readiness depends on traceable artifacts, relevant validation and a repeatable change process.