fix(agent): derive @version from BUILD_ID so Burrito re-extracts per build

Burrito keys its on-host install directory on `{release}_erts-{ertsver}_{appver}`
and skips extraction when `_metadata.json` is already present for that version.
With a static `@version "0.1.0"` in mix.exs, every new build landed in the same
cached dir on the target host — silently running stale code.

Now @version resolves to `0.1.0+<BUILD_ID>` where BUILD_ID is the git short SHA
(or `dev-<timestamp>` fallback). scripts/build-linux.sh computes it on the host
and passes it through Dockerfile.build's ARG/ENV, so every commit produces a
distinct Burrito install dir and fresh extraction is guaranteed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Carsten 2026-04-23 07:51:30 +02:00
parent 3367b95b91
commit 64dda9cb04
3 changed files with 24 additions and 3 deletions

View file

@ -28,6 +28,11 @@ COPY lib lib
COPY config config
RUN mix deps.compile
# BUILD_ID is injected by scripts/build-linux.sh (typically the git short SHA).
# Declared here — not earlier — so deps.compile stays cacheable across builds.
ARG BUILD_ID=dev
ENV BUILD_ID=${BUILD_ID}
RUN mix release
# Default: print the produced artifacts