You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have this stack of 3 PRs #30298 #30299 #30300
which I am upstreaming from my fork.
The most interesting one among them would be #30299, which carves out a pattern to enable building and testing bazel.git on non-google RBE platforms.
My hope is that we can codify these execution requirements as constraints that RBE vendors can then supply their own exec platforms to match them.
Looking forward to hearing what the Bazel team has to say about this setup
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I have this stack of 3 PRs
#30298
#30299
#30300
which I am upstreaming from my fork.
The most interesting one among them would be #30299, which carves out a pattern to enable building and testing bazel.git on non-google RBE platforms.
My hope is that we can codify these execution requirements as constraints that RBE vendors can then supply their own exec platforms to match them.
Looking forward to hearing what the Bazel team has to say about this setup
You can find my actual fork here https://github.com/sluongng/bazel-rbe/commits/master/, where I have been using BuildBuddy RBE + Workflows to test Bazel.git since Dec 2025. Some interesting stats:
Last 7 days flake detection:
All reactions