Delivery & Release Engineering
General material on getting a change from commit to production safely and often.
3 to work through
-
beginner
Your pipeline promotes one container digest from staging to production, and the team says production therefore runs exactly what was tested. The deployment chart values, the feature-flag defaults and the migration set are each resolved fresh at deploy time. Why is the promotion claim false, and what is the smallest change that makes it true?
3 min answer -
intermediate
A platform's pipeline is reliable but slow, and developers batch changes to avoid it. What is the real cost, and what should be measured?
2 min answer -
intermediate Multiple choice
Your pipeline takes 45 minutes and fails randomly twice a week. Which do you fix first and why?
2 min answer
3 terms in this topic
Delivery Pipelines
The automated path from commit to production — where speed and trustworthiness determine whether anyone uses the feedback it produces.
conceptPipeline Stage Contract
What each pipeline stage promises the next — an artifact of a stated shape plus a specific claim about it that has been verified.
conceptRelease Unit
The complete set of inputs a promotion must move together - artefact digest, configuration revision, flag defaults and schema version - because promo…
Neighbouring topics
Pipeline Architecture
Stages, fan-out, caching, and the difference between a pipeline and a long script.
Build Reproducibility
Pinned inputs and hermetic builds, so one commit cannot produce two different artifacts.
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
Environment Strategy
How many environments earn their cost, what each proves, and what none of them prove.
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Continuous Integration Discipline
Integrating to the mainline daily, and the test speed and review culture that requires.
Deployment Strategies
Rolling, blue-green, canary and shadow, and the traffic and state each one assumes.
Progressive Delivery
Separating deploy from release, and exposing a change to users in controlled increments.
Rollback & Forward Fix
When reversing is genuinely possible, and designing so that it usually is.
Database Migration Under CD
Expand-contract, backwards-compatible schema change, and migrations that cannot roll back.
GitOps
Declared desired state in version control, with a reconciler closing the gap continuously.
IaC Modules & Drift
Reusable infrastructure modules, state ownership, and detecting what changed out of band.
Policy as Code
Encoding standards as automated admission and plan-time checks instead of review comments.
Pipeline Secrets
Short-lived credentials, workload identity, and why the CI system is a prime target.
Supply-Chain Provenance
SBOMs, signed artifacts, attestation, and knowing what actually went into a build.
Deployment Gates
Automated verification between stages, and the difference between a gate and a delay.
Flow Metrics
Work in progress, flow time and flow efficiency — where a change waits rather than moves.
Change Management vs CD
Reconciling CAB-era controls with continuous delivery without pretending either away.
Multi-Region Rollout
Ordering regions, bake time, and stopping a bad change before it becomes global.