release/reproducible-build
Release builds are reproducible
A capability: each stack checks it with its own tools. Implemented for any, dotnet, go, java, kotlin, rust.
Combine: any. One implementation passing is enough: this belongs to the repository, not to each stack, so the stack that does it decides and the others pass with it.
| Severity | info |
| Tiers | 1 |
| Stacks | any |
| Scope | root |
| Kind | capability |
| Source | library v0.2.0 |
| Selected by | fleetlint-recommended@v0.2.0 |
Requirement
The release build removes what differs between two builds of the same commit: local paths and timestamps. The stack’s build settings do it, or SOURCE_DATE_EPOCH is set for the release build (in a tag-triggered CI file or the task runner).
Why
When anyone can rebuild a release bit for bit from the tag, a tampered artifact or a compromised build machine shows up as a mismatch.
Applies when
release.existsFix
Set the stack’s reproducibility options in the release build (see https://reproducible-builds.org/docs/) and export SOURCE_DATE_EPOCH from the commit time.
Agent instruction: Add the stack’s reproducibility settings to the release build and derive SOURCE_DATE_EPOCH from git log -1 --format=%ct; do not change what is built.
See: https://fleetlint.org/baseline/#releases, https://reproducible-builds.org/docs/
Generated by fleetlint docs from catalog v0.2.0.