Skip to content

[ci] Always use setup-bazel action - #9383

Merged
PeterJohnson merged 1 commit into
wpilibsuite:mainfrom
auscompgeek:bazel-gha-cache-downloads
Sep 5, 2026
Merged

[ci] Always use setup-bazel action#9383
PeterJohnson merged 1 commit into
wpilibsuite:mainfrom
auscompgeek:bazel-gha-cache-downloads

Conversation

@auscompgeek

Copy link
Copy Markdown
Member

See #9341 (comment)

The setup-bazel action handles putting the output root in an appropriate place, so we don't have to do it ourselves.

Also disable saving to GitHub Actions cache from PRs to avoid using up the limited cache space.

@auscompgeek
auscompgeek requested a review from a team as a code owner September 5, 2026 13:21
@github-actions github-actions Bot added the build Monorepo organization, Gradle/CMake/Bazel, upstream_utils, etc label Sep 5, 2026
@PeterJohnson
PeterJohnson merged commit 2f1a260 into wpilibsuite:main Sep 5, 2026
49 of 50 checks passed
AustinSchuh added a commit to AustinSchuh/allwpilib that referenced this pull request Sep 6, 2026
…ndbox

setup-bazel now runs on every platform (wpilibsuite#9383), so Windows already goes
through Bazelisk and gets an output base on D: without the if statement
this branch had added.  Take main's workflow as-is.

Signed-off-by: Austin Schuh <austin.linux@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Monorepo organization, Gradle/CMake/Bazel, upstream_utils, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants