ci(setup-minimal): route package-cache reads through the R2 mirror - #617
ci(setup-minimal): route package-cache reads through the R2 mirror#617bryan-minimal wants to merge 1 commit into
Conversation
Same change as webapp#380, with the bill quantified: the six per-PR advisory workflows each cold-pull ~6.5 GB of toolchain artifacts from GCS on fresh Azure runners — ~370 GB/week across ~174 runner IPs, the majority of remaining billed GCS egress. cache.minimal.farm serves the identical immutable sha256-verified objects from R2 with zero egress; every build on the unstable channel honors MINIMAL_REMOTE_CACHE_URL (minimal#643, canaried by minimal#667). Replaces #613, which accidentally swept unrelated working-tree files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Included review availability: 1 review is currently available. Based on recent review activity, included reviews refill at 2 per hour. 📝 WalkthroughWalkthroughThe minimal setup action now exports the R2 mirror URL through ChangesPackage cache mirror
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This localized CI configuration change reroutes package-cache reads through the mirror; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Replaces #613 — that PR accidentally included unrelated working-tree files (my
git add -Ain a live checkout; the WIP has been restored to its owner untouched). This one is the intended single-file change.One step added to the shared
setup-minimalaction, mirroring webapp#380 — with the bill quantified.Why: the six per-PR advisory workflows (smoke-test-coverage, corresponding-source, stable-closure-check, trivial-update, license-lint, version-age) each run on a fresh GitHub-hosted Azure runner and cold-pull ~6.5 GB of toolchain artifacts from GCS in
90 seconds. Across the fleet that's ~370 GB/week from ~174 runner IPs — the majority of remaining billed GCS egress ($250 CAD/mo at current pace). Attribution from GCS usage logs, timestamp-matched to this repo's workflow launch batches (runner IP active 21:22–21:24 ↔ workflows launched 21:22:13).Why it's safe:
cache.minimal.farmserves the identical immutable objects from R2 (verified byte-identical against authoritative GCS); the CLI sha256-verifies every artifact regardless of source;MINIMAL_REMOTE_CACHE_URLis honored by every build on theunstablechannel (minimal#643) and continuously canaried by minimal's dogfood lane (minimal#667). webapp has run this way since July 8. Rollback = delete the step.(Uses
.farmfor now — it flips tocache.minimal.devfor free when minimal#1234 makes that the client default, at which point this step becomes a harmless no-op that can be deleted.)🤖 Generated with Claude Code
Summary by CodeRabbit