You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c70e828
Browse filesBrowse the repository at this point in the historyBrowse files
ci: move the last VM-runner jobs to protected GKE runners
release.yml (release, the linux-x86_64 prebuilt cell, notify-hub), promote-baseline.yml, docs-post.yml and
release-ruleset-probe.yml leave the always-on pf-gcp-main/pf-gcp-post VMs for exact gkp-* pins in the protected runner
group. The x86_64 release cell runs on gkp-16cpu-32gb-amd64-128gb, installs Eigen in the job and asserts exactly
3.4.0 before CMake. actionlint labels, the preflight pins, a group-15 runner mirror, tests and docs follow; the retired
VM labels stay refused.
docs/ci.md sentences this commit removes because the pf-gcp-main/pf-gcp-post VM routing they describe is gone:
- "Release and baseline promotion retain their separate `pf-gcp-main` policy." (introduced by 3a0d150)
- "`release`, `notify-hub`, Linux x64 `prebuilt` and baseline `promote` use `["self-hosted","pf-gcp-main"]`."
(introduced by 3a0d150)
- "Before a workflow file moves onto a gke- or gkp- label, add its line to `.github/runner-group-allowlist.txt` and
ask for the org runner-group entry" (introduced by 6dd5287; replaced by the group-15 mirror sentence)
- "Rollback may restore an earlier GCP fleet pin; paid larger-runner labels remain refused." (introduced by 8154993)
- "Release and promotion use the isolated release fleet:" (introduced by 833f7ac)
- "`pf-gcp-main` admits only allowlisted workflows (an org runner-group restriction), so the one-time probe uses
`pf-gcp-post`." (introduced by 9c18d41)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments