Uh oh!
There was an error while loading. Please reload this page.
ci: enable bazel-diff - #3838
Conversation
We set USE_BAZEL_DIFF=1 in the reusable task configuration to activate bazel-diff target filtering in our CI pipelines.
There was a problem hiding this comment.
Code Review
This pull request configures the environment variable USE_BAZEL_DIFF to be enabled globally within the reusable configuration of the Bazel CI presubmit pipeline. The feedback highlights that running bazel-diff across all platforms and tasks is highly inefficient and may cause compatibility issues on certain runners like Windows. It is recommended to compute the changed targets once in a preliminary step instead.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Uh oh!
There was an error while loading. Please reload this page.
| skip_in_bazel_downstream_pipeline: "Bazel 7 required" | ||
| .reusable_config: &reusable_config | ||
| environment: | ||
| USE_BAZEL_DIFF: "1" |
There was a problem hiding this comment.
Where is this env var used? Is it baked into .bazelci config outside of the rules_python repo or something?
I was trying to look up what exactly it would end up doing. I know about https://github.com/Tinder/bazel-diff but we don't have it as a bazel_dep.
There was a problem hiding this comment.
rickeylev
commented
Jun 20, 2026
I think this broke CI. I think that what happened is the first enabling of bazel-diff skips running it entirely. Subsequent runs use it, but it tries to run targets with target_compatible_with set, then fails. |
Enable bazel-diff to improve CI performance by skipping targets that aren't affected by a PR