3 ms·

I struggled with this when trying to build a system where the output of a PR is labeled in such a way that once it is merged, it can be relabeled without rebuil

I struggled with this when trying to build a system where the output of a PR is labeled in such a way that once it is merged, it can be relabeled without rebuilding. I ended up taking the commit SHAs of parents of the virtual merge commit and label my containers with that. Then, when the PR is merged in, I have the same parent SHAs, and I can now move the label from a PR candidate to what is now on main. For provenance reasons I only want to build the code once. If the code doesn't change the checksum of the binary shouldn't.

fragmede 2y ago
except that usually timestamps get embedded into something somewhere, so the binary's checksum does change with each build.
- klodolph 2y ago
  Practically speaking that’s often true, but there are also projects where someone has figured out deterministic builds. There’s usually not a technical reason why you can’t have a deterministic build, but rather, it’s a question of whether you care to spend the resources making it happen (usual answer is “no”).