Consolidate Bazel CI setup into prepare-bazel-ci (#56222)

## What changed

Move the Bazel installation, repository cache configuration, and Windows MSVC environment setup directly into `prepare-bazel-ci`, and remove the `setup-bazel-ci` action. Wire the repository cache output and restore step to the inlined configuration step.

Update the Windows PATH script documentation and remove the deleted action from V8 canary path matching.

GitOrigin-RevId: 2472372478e1618cd03e98a1536f862f47352659
This commit is contained in:
Adam Perry @ OpenAI
2026-10-22 17:09:38 +00:00
committed by copyberry
parent 96a0d8d551
commit 9cb547349e
4 changed files with 82 additions and 102 deletions
@@ -8,7 +8,7 @@ This script derives a smaller, cache-stable PATH that keeps the Windows
toolchain entries Bazel-backed CI tasks need: MSVC and Windows SDK paths,
MinGW runtime DLL paths for gnullvm-built tests, Git, PowerShell, Node, Python,
DotSlash, and the standard Windows system directories.
`setup-bazel-ci` runs this after exporting the MSVC environment, and the script
`prepare-bazel-ci` runs this after exporting the MSVC environment, and the script
publishes the result via `GITHUB_ENV` as `CODEX_BAZEL_WINDOWS_PATH` so later
steps can pass that explicit PATH to Bazel.
#>
-1
View File
@@ -20,7 +20,6 @@ ROOT = Path(__file__).resolve().parents[2]
# workflow changes because they can alter whether the canary is invoked.
CANARY_PATH_PATTERNS = {
".bazelrc",
".github/actions/setup-bazel-ci/**",
".github/actions/prepare-bazel-ci/**",
".github/actions/setup-ci/**",
".github/scripts/run_bazel_with_buildbuddy.py",