Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

55059 Commits

276 Branches

378 Tags

1.2 GiB

Tag: Branch: Tree: e7fb03d8aa

Commit Graph

Author	SHA1	Message	Date
Jan Tattermusch	dc635afc61	[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
Jan Tattermusch	eae3082829	[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

Author

SHA1

Message

Date

Jan Tattermusch

dc635afc61

[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

Jan Tattermusch

eae3082829

[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

2 Commits (e7fb03d8aa1bb0d3ad8b85f0817f3127f3a1cc25)