Hosting & Deployment

Design a Safe Continuous Delivery Pipeline

Promote verified artifacts through environments with approvals, traceability, and rollback options.

Continuous delivery makes deployable software available through a repeatable process. The pipeline should promote the same artifact through environments rather than rebuilding slightly different outputs at each stage.

Build once and identify the artifact

Attach a version, commit reference, and build metadata to each artifact. Store it in a controlled registry or artifact repository. Deployment records should make it possible to identify exactly what is running.

Separate deployment from release

A deployment places code into an environment; a release exposes functionality to users. Feature flags, staged rollout, and configuration can separate these operations and reduce risk.

Add environment controls

Use environment-specific secrets and configuration. Require approval for production when the risk profile demands it. Avoid copying production secrets into development or test environments.

Plan rollback and forward recovery

Some database migrations are not safely reversible. Use expand-and-contract patterns, backups, and compatibility windows. Define whether recovery means redeploying an earlier artifact, disabling a feature, or applying a forward fix.

Checklist

  • Build an immutable, identifiable artifact.
  • Promote the same artifact across environments.
  • Separate deployment from feature release.
  • Protect production credentials.
  • Test rollback and forward-recovery procedures.
Share this page Help other developers discover this resource.