ci: restore intra-run .turbo cache fan-out to cut CI compute - #8186
Draft
y-lakhdar wants to merge 1 commit into
Draft
ci: restore intra-run .turbo cache fan-out to cut CI compute#8186y-lakhdar wants to merge 1 commit into
y-lakhdar wants to merge 1 commit into
Conversation
After #8146, every CI job re-primed the full Turbo graph from the remote cache (~60s/job, ~57 remote fetches) because the build->consumers artifact fan-out was removed. Publish the build job's .turbo once as a per-run artifact and have consumer jobs restore it for local cache hits, while keeping turbo.json remoteCache + TURBO_TOKEN for cross-run/branch/local reuse.
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restores the intra-run
.turbocache fan-out (build once → share as one artifact) that #8146 removed, layered on top of Turbo remote caching, to cut CI compute. Spike — draft until measured and reviewed.What it does
turbo buildinsetupand restored the whole graph from the remote cache (~60s/job; theRun unit testsjob showed57 cached / 62 tasksin ~61s). With ~70 jobs that added roughly +57 job-min per fullmerge_grouprun (total ~248 → ~291 job-min), and CI got marginally slower rather than faster.buildjob now publishes its.turboonce as a per-run artifact (save-cache: 'true'), andneeds: buildconsumers restore it (defaultload-cache: 'true') for local cache hits instead of each re-fetching ~57 task outputs from the remote cache.continue-on-error): on a miss, turbo falls back to the remote cache.turbo.jsonremoteCache+TURBO_TOKENare unchanged, so cross-run / cross-branch / local-dev reuse is preserved.pr-report,build-windows(different runner OS → different artifact), andbuild-missingopt out viaload-cache: 'false'.How to evaluate
Compare median total job-minutes of
merge_groupruns against the current baseline (~291 job-min), targeting a return to ≲250. Also spot-check a consumer job'ssetupstep duration (was 119s onRun unit tests, ~60s of it remote turbo restore).