Skip to content

Conversation

@lloeki
Copy link
Member

@lloeki lloeki commented Jun 24, 2025

BUNDLE_BIN is a path that is supposed to be specific to a given bundle. As such it cannot and should not be reused.

This manifests as bundle-specific path entries being hardcoded in scripts of a potentially shared bin folder. As a consequence the scripts can fail unless paths happen to be identical by sheer coincidence.

A number of additional fixes and improvements were made along the way:

  • There's a .repro_run_key file and REPRO_RUN_KEY build arg to control image consistency/external dependency closure via cache/layer cache usage
  • SOURCE_DATE_EPOCH is also enabled in CI (pinned to 1980 until everything can be reliably captured or inferred from the commit, after which commit will be used), same as for rake
  • To ensure more cache hits, parent lookup was increased to 10 (1 was just way too low)
  • Build args were not consistently used, causing occasional cache misses. Some day CI shoudl really be ported ot leverage the rake task

`BUNDLE_BIN` is a path that is supposed to be specific to a given
bundle. As such it cannot and should not be reused.

This manifests as bundle-specific path entries being hardcoded in
scripts of a potentially shared `bin` folder. As a consequence the
scripts can fail unless paths happen to be identical by sheer
coincidence.
@lloeki lloeki requested a review from a team as a code owner June 24, 2025 15:32
lloeki added 3 commits June 25, 2025 10:05
This forces a rebuild because 2.6 debian is outdated and misses `git`.

THs also makes local and CI build consistent.
This makes it consistent with rake
@lloeki lloeki force-pushed the lloeki/remove-bundle-bin branch from 9113761 to 8af99a8 Compare June 25, 2025 08:05
@lloeki lloeki merged commit 1dd22b5 into main Jun 25, 2025
120 of 121 checks passed
@lloeki lloeki deleted the lloeki/remove-bundle-bin branch June 25, 2025 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants