Compare commits

...
Sign in to create a new pull request.

1 commit

Author SHA1 Message Date
Julian Knutsen
da398036bd ci(bazel): cover fork and Dependabot PRs with the Bazel lanes (BAZEL_COVERS_FORKS=true)
Fork and Dependabot PRs ran both stacks: the legacy embedded, proxied,
server-storage and PR-lane tiers plus the Bazel lanes, which rbe-fork has
executed remotely (fork-ro/fork-rw) since the canary ended. Flip the
committed flag in pr.yml and pr-risk.yml so bazel-coverage retires those
tiers for forks too. A covered run the mint does not serve (mode cache)
already turns CI Gate / Required red with a re-run message; it never falls
back silently.

Refs ga-96smfk.15

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-06 20:24:35 +00:00
3 changed files with 18 additions and 9 deletions

View file

@ -42,10 +42,14 @@ env:
# flags above then retire their legacy tiers too): rbe-west's mint
# (rbe-fork) gives their Bazel lanes remote execution, instance oss-fork
# or, for allowlisted authors, oss, and a run the mint does not serve
# (mode cache) is red. "false": they keep the legacy tiers, and the Bazel
# lanes run remotely beside them whenever rbe-fork is open (bazel.yml
# modes fork-ro/fork-rw), else locally with the read-only cache as before.
BAZEL_COVERS_FORKS: "false"
# (mode cache) is red, never a silent fall back to the legacy tiers.
# "false": they keep the legacy tiers, and the Bazel lanes run remotely
# beside them whenever rbe-fork is open (bazel.yml modes
# fork-ro/fork-rw), else locally with the read-only cache as before.
# "true" since ga-96smfk.15: after the canary every fork and Dependabot
# run took fork-ro/fork-rw (none fell to cache). Rollback if the mint
# becomes unreliable: commit "false" in both workflows.
BAZEL_COVERS_FORKS: "true"
jobs:
detect-ci-tier:

View file

@ -55,10 +55,14 @@ env:
# flags above then retire their legacy tiers too): rbe-west's mint
# (rbe-fork) gives their Bazel lanes remote execution, instance oss-fork
# or, for allowlisted authors, oss, and a run the mint does not serve
# (mode cache) is red. "false": they keep the legacy tiers, and the Bazel
# lanes run remotely beside them whenever rbe-fork is open (bazel.yml
# modes fork-ro/fork-rw), else locally with the read-only cache as before.
BAZEL_COVERS_FORKS: "false"
# (mode cache) is red, never a silent fall back to the legacy tiers.
# "false": they keep the legacy tiers, and the Bazel lanes run remotely
# beside them whenever rbe-fork is open (bazel.yml modes
# fork-ro/fork-rw), else locally with the read-only cache as before.
# "true" since ga-96smfk.15: after the canary every fork and Dependabot
# run took fork-ro/fork-rw (none fell to cache). Rollback if the mint
# becomes unreliable: commit "false" in both workflows.
BAZEL_COVERS_FORKS: "true"
# bazel.yml's bazel-cmd-dolt lane (the cmd/bd Dolt-server tier: the
# Dolt-gated cmd/bd tests no other lane runs) is advisory while this is
# "false": it runs and reports in the bazel call (continue-on-error, so a

View file

@ -998,7 +998,8 @@ manifests. On those PRs they are the tiers' only pre-merge run, and
policy-tested) is `"true"`: their lanes then run remotely through
rbe-fork (modes `fork-ro`/`fork-rw`), and a run rbe-fork does not serve
(mode `cache`) turns `CI Gate / Required` red rather than falling back.
It ships `"false"`.
It is `"true"` (ga-96smfk.15): fork and Dependabot PRs run only the Bazel
lanes for the retired tiers.
- Everyone else keeps the legacy tiers unchanged:
- fork PRs, while `BAZEL_COVERS_FORKS` is `"false"` (their Bazel lanes
run beside the legacy tiers: remotely while rbe-fork is open, else in