Repository navigation
ci: run Bazel Native nightly and on merge, not on every PR - #2880
Merged
MarcusSorealheis merged 4 commits intoOct 20, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
b7r6
force-pushed
the
ci/native-bazel-nightly
branch
from
October 3, 2026 21:33
b97038a to
9ef2426
Compare
b7r6
force-pushed
the
ci/native-bazel-nightly
branch
from
October 3, 2026 21:37
9ef2426 to
b97038a
Compare
b7r6
pushed a commit
to b7r6/nativelink
that referenced
this pull request
Oct 4, 2026
Combines TraceMachina#2877 + TraceMachina#2878 + TraceMachina#2880 on one branch so a single CI run shows the true end-state per-PR wall clock. Not for merge: the individual PRs are the review units; this exists to measure their net effect.
b7r6
pushed a commit
to b7r6/nativelink
that referenced
this pull request
Oct 4, 2026
Combines TraceMachina#2877 + TraceMachina#2878 + TraceMachina#2880 on one branch so a single CI run shows the true end-state per-PR wall clock. Not for merge: the individual PRs are the review units; this exists to measure their net effect.
This was referenced Oct 7, 2026
Closed
b7r6
added a commit
to b7r6/nativelink
that referenced
this pull request
Oct 7, 2026
…achina#2880) on fork main Mirrors the intended upstream per-PR layout ahead of land: Bazel Native and Cargo Native (incl. Windows) move to nightly + merge-to-main; per-PR build/test signal is carried by the Nix Bazel Dev lane. Keeps the fork representative of where upstream CI is going, not where main happens to sit today. TraceMachina#2897 retry logic preserved in native-bazel.yaml.
b7r6
added a commit
to b7r6/nativelink
that referenced
this pull request
Oct 7, 2026
Completes the no-per-PR-OCI-builds intent: image-off-pr moved image.yaml off PRs and TraceMachina#2877 moved the nix integration job off PRs, but main.yaml's integration-tests (docker-compose image build + run_integration_tests.sh) fell between them and still ran on every PR. Defer to nightly + merge-to-main, matching TraceMachina#2880's pattern. Fork-local until folded into the upstream OCI/nightly set.
b7r6
added a commit
to b7r6/nativelink
that referenced
this pull request
Oct 14, 2026
…achina#2880) on fork main Mirrors the intended upstream per-PR layout ahead of land: Bazel Native and Cargo Native (incl. Windows) move to nightly + merge-to-main; per-PR build/test signal is carried by the Nix Bazel Dev lane. Keeps the fork representative of where upstream CI is going, not where main happens to sit today. TraceMachina#2897 retry logic preserved in native-bazel.yaml.
b7r6
added a commit
to b7r6/nativelink
that referenced
this pull request
Oct 14, 2026
Completes the no-per-PR-OCI-builds intent: image-off-pr moved image.yaml off PRs and TraceMachina#2877 moved the nix integration job off PRs, but main.yaml's integration-tests (docker-compose image build + run_integration_tests.sh) fell between them and still ran on every PR. Defer to nightly + merge-to-main, matching TraceMachina#2880's pattern. Fork-local until folded into the upstream OCI/nightly set.
b7r6
force-pushed
the
ci/native-bazel-nightly
branch
from
October 14, 2026 17:40
b97038a to
fe3f097
Compare
The non-Nix Bazel Native lane (Bazel 9.1.1 + 8.7.0) duplicates the per-PR build/test signal from the Nix Bazel Dev lane. Drop its pull_request trigger (keep push:main, add schedule + workflow_dispatch) to take ~12 min off every PR; non-Nix build breakage is caught nightly and on merge.
b7r6
force-pushed
the
ci/native-bazel-nightly
branch
from
October 15, 2026 11:19
fe3f097 to
69a9699
Compare
This branch was successfully deployed
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
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.
What and why
Bazel Nativebuilds and tests with the non-Nix Bazel toolchain on every pull request: Bazel 9.1.1, plus an 8.7.0 leg that checks lockfile compatibility. Nix's Bazel Dev lane already runs the samebazel test //...on every PR. This moves Bazel Native to a nightly run plus every merge tomain, withworkflow_dispatchfor on-demand runs. Its runs onmaintoday took 7 to 11 minutes.How was this verified?
The workflow parses. The job matrix and every step are unchanged: the
pull_requesttrigger is removed,push: mainstays, andscheduleandworkflow_dispatchare added. It is not a required status check, so dropping the PR trigger doesn't block merges.Our fork's
mainhas run this schedule since 2026-10-14, and today's scheduled Bazel Native run there passed.Risk
This is the most debatable change in the CI-deferral set. A break in the non-Nix Bazel build, or in the 8.7.0 lockfile check, would be caught on merge or overnight instead of on the PR. People who build without Nix would see that breakage after merge.
Bazel Dev still builds and tests everything on each PR, and
push: mainkeeps a check at merge time. No source, config or wire-format changes. If you'd rather keep non-Nix Bazel on PRs, this is the one to drop.AI assistance
Claude drafted this change and description under my direction.