build
The automated step that turns source code into something runnable, and the result of that step.
In more detail
A green build means the configured checks passed; it is evidence, not proof of perfect software. A broken build should fail loudly at the first gate. In the twelve-factor app, build is the first of three separate stages and happens once per commit.
Related terms
- continuous integration — Automatically building and testing every change as soon as it is pushed, so problems are caught early.
- artifact — A file produced by a build, such as a compiled program or an image, that is stored and passed on to later steps.
- 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.
- quality gate — A check, or set of checks, that a change must pass before it can move on, such as being merged or promoted to the next pipeline stage.
Taught in
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering
- Trunk-Based Development Versus Git Flow — DevOps & Site Reliability Engineering
- Continuous Integration — DevOps & Site Reliability Engineering
- Building And Versioning The Artifact — DevOps & Site Reliability Engineering