Skip to content

release.yml: cache volume steps only on Namespace runners - #142

Merged
shinyobjectz merged 1 commit into
mainfrom
runner-cache-guard
Nov 13, 2026
Merged

shinyobjectz merged 1 commit into
mainfrom
runner-cache-guard

Conversation

@shinyobjectz

Copy link
Copy Markdown
Owner

Namespace's plan here can't start Windows machines ('not allowed to create windows/amd64 instances'), so Windows goes back to GitHub's runner. The cache-volume step (and skipping the target/ cleanup) now follow the runner itself (runner.name nsc-*) instead of the RELEASE_RUNNER_CACHE variable, which applied to every job. Mac and Linux stay on Namespace (RELEASE_MAC_RUNNER, RELEASE_LINUX_RUNNER).

The Namespace dry run of rc3's code (run 43485470105): Linux built cold in 9 minutes (the whole job 11) on a 32-core machine, against 105 on GitHub's.

…runner, nsc-*), not a repo variable: the Namespace plan has no Windows runners (not allowed to create windows/amd64 instances), so Windows builds on GitHub's runner with the R2 compile cache while the Mac and Linux keep their build folders on Namespace's volumes
@shinyobjectz
shinyobjectz merged commit ae49b9f into main Nov 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant