Guides
How to structure release builds
Release builds are slow and occasionally non-reproducible.
5 min read
Release builds are slow and occasionally non-reproducible.
Why it happens
Release pipelines float image versions and rebuild artefacts that were already tested.
How to fix it
- Pin runner images and base images by digest in release workflows
- Promote the artefact that passed tests rather than rebuilding
- Generate provenance and an SBOM during the release build
- Keep release workflows in a protected environment
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.