Continuous delivery
Continuous delivery prepares software changes for release through a repeatable process. Approval for production can remain a deliberate decision.
Continuous delivery, or CD, extends integration with a repeatable path to a releasable software version. Automated steps prepare the change and check it through the intended stages.
A hypothetical portal creates a package after checks and deploys it to the test environment. The responsible person then decides whether to switch production. With continuous deployment, that production step instead happens automatically after the planned checks. The abbreviation CD alone leaves this distinction unclear.
A prepared version is not automatically suitable for every use. Database changes, configuration and the rollback path must fit the particular switch. Which checks succeeded and which version was approved should remain traceable.
Sources
Related terms
- Continuous integrationContinuous integration regularly merges changes into a shared codebase. Automated checks can reveal certain conflicts earlier.
- Software releaseA software release is an identified software version made available for a particular use. Publishing it does not automatically switch every system to it.
- Feature flagA feature flag switches planned application behaviour through configuration. It can separate technical deployment from making a feature available.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support