build, release, run
Three strictly separate stages: build turns code into a bundle, release joins it to one deploy config with an identifier, and run starts processes from a chosen release.
In more detail
Factor V of the twelve-factor app. Releases form an append-only ledger and cannot be changed once created; any change is a new release. That makes rollback a selection of an earlier release, lets one tested bundle be promoted through every environment, and makes it impossible to edit code at run time.
Related terms
- build — The automated step that turns source code into something runnable, and the result of that step.
- release — Making a version of software, or one of its behaviours, available to users; also the versioned package being made available.
- release identifier — A unique name for one release, such as 2026.09.11-a1b2c3, that every running process and log line can report.
- append-only — Describes a record you can only add new entries to, never edit or delete existing ones.
- rollback — Returning a system to a previous known-good version after a bad change.
Taught in
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Building And Versioning The Artifact — DevOps & Site Reliability Engineering