30b3d5061a
- Add a new docker image "rbe_ubuntu2004" that is built in a way that's analogous to how our other testing docker images are built (this gives us control over what exactly is contained in the docker image and ability to fine-tune our RBE configuration) - Switch RBE on linux to the new image (which gives us ubuntu20.04-based builds) For some reason, RBE seems to have trouble pulling the docker image from Google Artifact Registry (GAR), which is where our public testing images normally live, so for now, I used a workaround and I upload a copy of the rbe_ubuntu2004 docker image to GCR as well, and that makes RBE works just fine (see comment in the `renerate_linux_rbe_configs.sh` script). More followup items (config cleanup, getting local sanitizer builds working etc.) are in go/grpc-rbe-tech-debt-2023 |
||
|---|---|---|
| .. | ||
| rbe_ubuntu2004 | ||
| rbe_win2019 | ||
| rbe_windows_bazel_5.2.0_vs2019 | ||
| BUILD | ||
| README.md | ||
| generate_linux_rbe_configs.sh | ||
README.md
RBE toolchain configuration (Linux and Windows)
-
rbe_ubuntu2004: Autogenerated toolchain configuration for linux RBE. Run
generate_linux_rbe_configs.shto regenerate. -
rbe_windows_bazel_5.2.0_vs2019: The autogenerated toolchain configuration for windows RBE. Note that the bazel version denotes the bazel version that was used to generate the toolchain configuration. The configuration can be use with different bazel versions (as long as it works). See go/rbe-windows-user-guide
-
rbe_win2019: The windows dockerfile to rebuild the docker image we use on RBE workers. See go/rbe-windows-user-guide