fix(ci): expose ACTIONS_* runtime env so the e2e gha build cache engages

[cyberantonz]

Problem

The Build runner image job in the E2E workflow takes ~13.5 min on every PR run — a full Rust recompile of analytics + identity-resolution + jira-enrich — even on PRs that touch no backend code and leave Cargo.lock unchanged (e.g. #1926, where all runs rebuilt from scratch).

BuildKit logs from those runs contain zero importing/exporting cache manifest steps: the type=gha cache wired in compose/docker-compose.cache.yml never engages.

Cause

The type=gha cache backend needs ACTIONS_RUNTIME_TOKEN / ACTIONS_CACHE_URL, which GitHub exposes only to JS actions. build-images.yml works because docker/build-push-action injects them; the E2E build runs ./e2e.sh build (docker compose build) in a plain run: step, so buildx finds no token and silently drops the cache_from/cache_to config.

Fix

Add crazy-max/ghaction-github-runtime@v3 (by the buildx maintainer, built for exactly this) before the build step — it exports the ACTIONS_* runtime env to run steps.

Expected effect

First run on this branch populates the cache; subsequent runs should show importing cache manifest from gha,scope=e2e-* and CACHED on the cargo dep layers, dropping the build job from ~13.5 min to ~2–4 min for PRs that don't touch backend code.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Improved end-to-end build performance by enabling Docker build caching in the CI workflow.
  • Reduced unnecessary full rebuilds during automated builds.

[coderabbitai]

📝 Walkthrough

Walkthrough

The E2E workflow now exposes GitHub Actions runtime cache variables before docker compose build, allowing Buildx cache configuration to be passed into the runner-image build.

Changes

E2E build cache runtime

Layer / File(s)	Summary
Expose runtime cache values .github/workflows/e2e-bronze-to-api.yml	Adds crazy-max/ghaction-github-runtime@v3 before the runner-image build to provide ACTIONS_RUNTIME_TOKEN and ACTIONS_CACHE_URL to Docker Compose.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: aleksdotbar, mozhaev-dev

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the workflow change and the cache-enabling runtime env exposure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

.github/workflows/e2e-bronze-to-api.yml (1)

88-94: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Refresh and pin the runtime action revision.

The integration point is correct, but upstream currently documents crazy-max/ghaction-github-runtime@v4; this workflow still uses @v3. Update to the supported revision and preferably pin its commit SHA to prevent unreviewed action changes. (github.com)

Proposed change

-      - uses: crazy-max/ghaction-github-runtime@v3
+      - uses: crazy-max/ghaction-github-runtime@v4 # preferably pin to a verified commit SHA

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/e2e-bronze-to-api.yml around lines 88 - 94, Update the
crazy-max/ghaction-github-runtime action reference in the workflow from the
outdated v3 revision to the currently supported v4 revision, preferably pinned
to its reviewed commit SHA. Preserve the existing workflow step and
runtime-token exposure behavior.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.github/workflows/e2e-bronze-to-api.yml:
- Around line 88-94: Update the crazy-max/ghaction-github-runtime action
reference in the workflow from the outdated v3 revision to the currently
supported v4 revision, preferably pinned to its reviewed commit SHA. Preserve
the existing workflow step and runtime-token exposure behavior.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9906fd16-d3e4-4281-af74-4e611ac1ca31

📥 Commits

Reviewing files that changed from the base of the PR and between dcec5bb and 8527d26.

📒 Files selected for processing (1)

• .github/workflows/e2e-bronze-to-api.yml