From 3da8717df4302aacd57fe0865d33234509b5b2f7 Mon Sep 17 00:00:00 2001 From: Anton Zelenov Date: Tue, 28 Jul 2026 13:28:53 +0800 Subject: [PATCH] fix(ci): expose ACTIONS_* runtime env so the e2e gha build cache engages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The e2e build job builds via docker compose in a plain run step, which never sees ACTIONS_RUNTIME_TOKEN/ACTIONS_CACHE_URL — buildx silently drops the type=gha cache_from/cache_to wired in docker-compose.cache.yml, so every PR run fully recompiled analytics + identity-resolution + jira-enrich (~13.5 min) even with an unchanged Cargo.lock. crazy-max/ghaction-github-runtime exports those env vars to run steps, letting the existing cache overlay actually restore the dep layers. Co-Authored-By: Claude Fable 5 Signed-off-by: Anton Zelenov --- .github/workflows/e2e-bronze-to-api.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/e2e-bronze-to-api.yml b/.github/workflows/e2e-bronze-to-api.yml index b19d84565..30794794b 100644 --- a/.github/workflows/e2e-bronze-to-api.yml +++ b/.github/workflows/e2e-bronze-to-api.yml @@ -85,6 +85,13 @@ jobs: # compose/docker-compose.cache.yml wires onto the build-only services. - uses: docker/setup-buildx-action@v3 + # Expose ACTIONS_RUNTIME_TOKEN / ACTIONS_CACHE_URL to run steps. The + # type=gha cache backend needs them; GitHub only hands them to JS + # actions, so `docker compose build` in a plain run step never sees + # them and buildx SILENTLY drops the cache_from/cache_to config — + # every run was a full Rust recompile. + - uses: crazy-max/ghaction-github-runtime@v3 + # ─── Build the runner image ───────────────────────────────────────── # The runner bakes in analytics + each connector's enrich binary, each # compiled FROM ITS OWN Dockerfile via build-only services wired as