Chiebot-Mirror
/
grpc
mirror of https://github.com/grpc/grpc.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
55782 Commits
276 Branches
377 Tags
1.2 GiB
Tag: Branch: Tree: 574b19ec31
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '574b19ec31'
${ noResults }
grpc/third_party/toolchains/README.md

38 lines
2.0 KiB
Raw Normal View History Unescape

Switch linux RBE to ubuntu18.04, get rid of rbe_autoconfig (#32559) First step in the modernization of our RBE stack (see go/rbe-tech-debt-notes). - Get rid of the deprecated rbe_autoconfig and start using [rbe_configs_gen](https://github.com/bazelbuild/bazel-toolchains#rbe_configs_gen---cli-tool-to-generate-configs) + check in the generated toolchain configs. - Switch from marketplace.gcr.io/google/rbe-ubuntu16-04 to marketplace.gcr.io/google/rbe-ubuntu18-04 (this image is still not owned by us, but at least it's newer and demonstrates how a switch to a newer docker image is done). - provide script for generating the linux RBE toolchain configs. - cleanup RBE configuration in the bazelrc files used for remote build
2 years ago
# RBE toolchain configuration (Linux and Windows)
[RBE windows] Use bazel 6.3.2 on windows RBE (after regenerating toolchain) (#34216) - Upgrade windows RBE builds to bazel 6.3.2 (supersedes https://github.com/grpc/grpc/pull/33880). To be able to do that, the RBE toolchain needed to be regenerated and - Also added "--dynamic_mode=off" option for windows build since it seemed necessary for bazel 6.x builds to pass. - Wrote instructions for generating windows RBE toolchain using the `rbe_configs_gen` tool (the original windows RBE toolchain was out of data and also it was generated by a custom script from go/rbe-windows-user-guide - using a standard tool is better) - Wrote instructions for rebuilding the windows RBE docker image. This addresses the problem where windows RBE is stuck on bazel 5.x (unlike the rest of the repository) and also documents the steps for making changes to the RBE docker image (e.g. upgrading the visual studio version used by RBE). Since we were planning on adding testing for VS2022 (for which we don't have any test ATM), this will definitely come handy. With the documentation the process should now be relatively straightforward.
1 year ago
## Linux
The `rbe_ubuntu2004` directory contains the autogenerated toolchain configuration for linux RBE.
Run `generate_linux_rbe_configs.sh` to regenerate.
migrate windows RBE to win2019 pool
5 years ago
[RBE windows] Use bazel 6.3.2 on windows RBE (after regenerating toolchain) (#34216) - Upgrade windows RBE builds to bazel 6.3.2 (supersedes https://github.com/grpc/grpc/pull/33880). To be able to do that, the RBE toolchain needed to be regenerated and - Also added "--dynamic_mode=off" option for windows build since it seemed necessary for bazel 6.x builds to pass. - Wrote instructions for generating windows RBE toolchain using the `rbe_configs_gen` tool (the original windows RBE toolchain was out of data and also it was generated by a custom script from go/rbe-windows-user-guide - using a standard tool is better) - Wrote instructions for rebuilding the windows RBE docker image. This addresses the problem where windows RBE is stuck on bazel 5.x (unlike the rest of the repository) and also documents the steps for making changes to the RBE docker image (e.g. upgrading the visual studio version used by RBE). Since we were planning on adding testing for VS2022 (for which we don't have any test ATM), this will definitely come handy. With the documentation the process should now be relatively straightforward.
1 year ago
## Windows
migrate windows RBE to win2019 pool
5 years ago
[CI] Updated RBE Windows Configuration to use Bazel 7.3.1 (#38006) The Windows RBE test has been using Bazel 7.3.1 for running tests. However, the RBE configuration itself was built with an older Bazel version (6.3.2). While this hasn't caused any issues so far, it's best to use the same Bazel version (7.3.1) for both building the RBE configuration and running tests to ensure consistency and avoid potential problems in the future. Related to https://github.com/grpc/grpc/pull/37987
4 weeks ago
The `rbe_windows_bazel_7.3.1_vs2019` directory contains the autogenerated toolchain configuration for windows RBE.
[RBE windows] Use bazel 6.3.2 on windows RBE (after regenerating toolchain) (#34216) - Upgrade windows RBE builds to bazel 6.3.2 (supersedes https://github.com/grpc/grpc/pull/33880). To be able to do that, the RBE toolchain needed to be regenerated and - Also added "--dynamic_mode=off" option for windows build since it seemed necessary for bazel 6.x builds to pass. - Wrote instructions for generating windows RBE toolchain using the `rbe_configs_gen` tool (the original windows RBE toolchain was out of data and also it was generated by a custom script from go/rbe-windows-user-guide - using a standard tool is better) - Wrote instructions for rebuilding the windows RBE docker image. This addresses the problem where windows RBE is stuck on bazel 5.x (unlike the rest of the repository) and also documents the steps for making changes to the RBE docker image (e.g. upgrading the visual studio version used by RBE). Since we were planning on adding testing for VS2022 (for which we don't have any test ATM), this will definitely come handy. With the documentation the process should now be relatively straightforward.
1 year ago
The configuration was generated by the `rbe_configs_gen` tool (just as the linux RBE config),
but since it's a windows configuration, it needs to be run on a windows machine.
In order to regenerate:
- Clone `grpc` repository in a kokoro debug windows VM (see internal documentation for how to create one)
- Run `generate_windows_rbe_configs.sh` to regenerate the configs locally on the VM.
- Copy the generated configs back to your workstation (e.g. via `gcloud compute scp` command)
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).
Also see go/rbe-windows-user-guide
# Windows RBE docker image
[bazel rbe] Update RBE windows docker image (and move it to GAR) (#34229) - Update to windows RBE docker image, followed by subsequent regenerate of win RBE toolchain (basically verifying that the README.md for windows RBE toolchain works well) - Also move windows docker image from GCR to GAR (which is where our other testing images already live). - (cleanup) Move windows RBE docker image to a better location in our repo. This PR should be sufficient to demonstrate how we would go about upgrading the windows RBE build to VS2022 once needed.
1 year ago
The `dockerfile/rbe_windows2019` directory contains the dockerfile to rebuild the docker image we use on RBE windows workers. See go/rbe-windows-user-guide.
[RBE windows] Use bazel 6.3.2 on windows RBE (after regenerating toolchain) (#34216) - Upgrade windows RBE builds to bazel 6.3.2 (supersedes https://github.com/grpc/grpc/pull/33880). To be able to do that, the RBE toolchain needed to be regenerated and - Also added "--dynamic_mode=off" option for windows build since it seemed necessary for bazel 6.x builds to pass. - Wrote instructions for generating windows RBE toolchain using the `rbe_configs_gen` tool (the original windows RBE toolchain was out of data and also it was generated by a custom script from go/rbe-windows-user-guide - using a standard tool is better) - Wrote instructions for rebuilding the windows RBE docker image. This addresses the problem where windows RBE is stuck on bazel 5.x (unlike the rest of the repository) and also documents the steps for making changes to the RBE docker image (e.g. upgrading the visual studio version used by RBE). Since we were planning on adding testing for VS2022 (for which we don't have any test ATM), this will definitely come handy. With the documentation the process should now be relatively straightforward.
1 year ago
Note that for linux, we use a docker image under `tools/dockerfile` (since for Linux RBE docker image is simply of the testing docker images
we maintain)
## How to rebuild the Windows RBE docker image and use it for Windows RBE
On a kokoro debug windows VM, run the following:
[bazel rbe] Update RBE windows docker image (and move it to GAR) (#34229) - Update to windows RBE docker image, followed by subsequent regenerate of win RBE toolchain (basically verifying that the README.md for windows RBE toolchain works well) - Also move windows docker image from GCR to GAR (which is where our other testing images already live). - (cleanup) Move windows RBE docker image to a better location in our repo. This PR should be sufficient to demonstrate how we would go about upgrading the windows RBE build to VS2022 once needed.
1 year ago
- `docker build -t us-docker.pkg.dev/grpc-testing/testing-images-public/rbe_windows2019 third_party/toolchains/dockerfile/rbe_windows2019`
[RBE windows] Use bazel 6.3.2 on windows RBE (after regenerating toolchain) (#34216) - Upgrade windows RBE builds to bazel 6.3.2 (supersedes https://github.com/grpc/grpc/pull/33880). To be able to do that, the RBE toolchain needed to be regenerated and - Also added "--dynamic_mode=off" option for windows build since it seemed necessary for bazel 6.x builds to pass. - Wrote instructions for generating windows RBE toolchain using the `rbe_configs_gen` tool (the original windows RBE toolchain was out of data and also it was generated by a custom script from go/rbe-windows-user-guide - using a standard tool is better) - Wrote instructions for rebuilding the windows RBE docker image. This addresses the problem where windows RBE is stuck on bazel 5.x (unlike the rest of the repository) and also documents the steps for making changes to the RBE docker image (e.g. upgrading the visual studio version used by RBE). Since we were planning on adding testing for VS2022 (for which we don't have any test ATM), this will definitely come handy. With the documentation the process should now be relatively straightforward.
1 year ago
- To be able to authenticate when pushing the image to GAR, run `gcloud auth configure-docker us-docker.pkg.dev`
- `docker push us-docker.pkg.dev/grpc-testing/testing-images-public/rbe_windows2019`
- Update the `generate_windows_rbe_configs.sh` with the newly built & pushed image's SHA256 digest.
- Regenerate the Windows RBE toolchain with the instructions above.