ci: canary — migrate verify-rules now that Bazel is on smithy#4
Open
ci: canary — migrate verify-rules now that Bazel is on smithy#4
Conversation
…stalled Smithy main commit c5d4794 added bazelisk + buildifier + OpenJDK 21 to the host. This is the validation canary for that change: pick the smallest Bazel-using job in any pulseengine repo and flip its runs-on to smithy. verify-rules is just two bazel query calls. No compile, no Lean toolchain download. bazelbuild/setup-bazelisk@v3 stays in the workflow; it is a no-op when bazel is already on PATH. If this lands green, it unblocks ~30 hosted jobs across rules_*, wasm-component-examples, moonbit_checksum_updater, and loom's rocq-proofs. Phase C of the Bazel rollout.
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
1 participant
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
Smithy main commit
c5d4794(feat(toolchains): add Bazel viabazelisk + buildifier + JDK 21) made bazel/bazelisk/buildifier
available on the self-hosted fleet. This is the single-job
canary validating that change before we batch-migrate the
remaining ~30 Bazel-using jobs across pulseengine repos.
What's migrated
Only
verify-rules— twobazel querycalls (//lean/...and//aeneas/...). No compile, no Lean toolchain download, completesin seconds. If this passes, the host setup is correct end-to-end.
What stays on hosted
The
buildmatrix job (ubuntu-latest+macos-latest). ThemacOS half can't migrate; splitting the matrix is a separate PR
once this canary proves out.
Why this validates the whole rollout
bazel queryexercises the full bazelisk → bazel → JDK chainwithout compile cost:
.bazelversion(or its default), downloads theright Bazel into
~/.cache/bazelisk/Anything wrong with the host setup (missing JDK, broken bazelisk,
PATH issue, permissions) shows up here in seconds.
Test plan
lightrunnerjournalctl -u smithy-trace-eacces.service~/.cache/bazeland~/.cache/bazeliskpopulate under the runner homeAfter this lands
Spawn batch agents for:
rules_wasm_component,rules_rocq_rust,rules_lean(the build matrix's Linux side),rules_moonbit,wasm-component-examples,moonbit_checksum_updater,loom. Eachgets its own PR migrating the Bazel jobs we previously had to leave
on
ubuntu-latest.Rollback
Revert this commit; verify-rules flips back to
ubuntu-latest.