-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows RBE Tracking Issue #10619
Comments
@nicolasnoble can you share the gRPC experience with RBE here? |
cc @jtattermusch - we've been able to run Windows RBE after a lot of tweaks in our environment: https://github.com/grpc/grpc/blob/cc43fd64ab97e45fcdd38759dd8d9eb273823b9e/third_party/toolchains/BUILD#L21 |
Ah cool, this dockerfile should be a good reference: https://github.com/grpc/grpc/blob/master/third_party/toolchains/bazel_0.26.0_rbe_windows/Dockerfile |
Can you speak to what sorts of tweaks you had to make and if the RBE product is available for us to use with Windows? |
Also see https://github.com/grpc/grpc/pull/22473/files which migrates our stack to Win2019 workers (which is what you should use if you wanna go ahead with windows RBE). What we've done for RBE windows:
|
I joined a google group and got access to some docs, not seeing any mention of Windows yet but that is a start, I'll keep looking for more docs and see if I can bother someone to get access +1 to Windows 2019, we're working on a Dockerfile etc. to get that going and will make a PR to https://github.com/envoyproxy/envoy-build-tools Thanks for the resources/tips, we will hopefully make some progress soon and maybe have more questions |
PR for docker image: envoyproxy/envoy-build-tools#40 Confirmed that it locally has the dependencies to build envoy-static.exe and tests |
so far I don't see any flags to be able to choose the OS of the worker pool VMs in the docs: https://cloud.google.com/remote-build-execution/docs/set-up/remote-environment#create_a_worker_pool, does that sound like something that is available in some further hidden docs? |
@jtattermusch could you shed some light on this comment/link? https://github.com/jtattermusch/grpc/blob/f654f8159778d8b6807ddbd8b20bdeb686a5a819/third_party/toolchains/rbe_win2019/Dockerfile#L62-L63 I believe we're running into the same issue on Azure Pipelines which has a recent/latest version of Docker (19.03.5). We have a local version of Docker thats on an older version (18.09.0) and |
The way a windows pool is setup internally is to create a regular linux pool and the file a ticket with the RBE team to switch your pool to windows OS (it's not self-service). So I guess you'll need to ask the RBE team if this is possible for external users. |
a relevant bazel issue for this work: bazelbuild/bazel#11101 |
We've hacked together some changes to |
Our next step is to get a test GCP environment with RBE + Windows enabled to test out our generated toolchain |
|
PR to enable remote cache in CI: #10831 |
We're testing out our generated toolchain config and toolchain image and with a few tweaks are so far successfully building Envoy with RBE, forthcoming PRs to upstream our work coming soon |
We've started a Draft PR here to demonstrate a working RBE build on Windows workers: #11107 this should get turned into a full PR once we have upstreamed all our changes to the bazel-toolchains and envoy-build-tools dependencies |
This build log demonstrates a working build in CI that builds all sources and compiles tests not tagged with |
See envoyproxy/envoy-build-tools#64 for changes to envoy-build-tools that will enable generating Windows toolchain configs. All changes required for bazel-toolchains have been merged in: bazelbuild/bazel-toolchains#873 |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
Our toolchain config changes have all been merged, we're just waiting on fixing some Windows specific issues caused by the merge of recent PRs |
Commit Message: Enable RBE build in Windows CI - Bumps envoy-build-tools and bazel-toolchains - Bumps envoy-build-ubuntu image tag - Running Windows CI via docker uses the same mechanism as Linux to find the image tag, the tags are the same for Windows and Linux images - Temporarily adds a patch to fix rules_go for Windows RBE issue executing batch scripts, see #11657 - Tags/fixes some additional tests that fail in CI Additional Description: N/A Risk Level: Low, but we may observe differences in performance of Windows CI running remotely, we may need to adjust the worker pool accordingly Testing: N/A Docs Changes: N/A Release Notes: N/A Fixes #10619 Signed-off-by: Sunjay Bhatia <sbhatia@pivotal.io> Co-authored-by: William A Rowe Jr <wrowe@vmware.com>
Description:
We have started extending and enabling what is run in the Windows CI pipeline and found the Azure Pipelines build environment is severely underpowered to do a fully local build in a timely manner. While we may look in to using a user-managed Azure Pipelines worker, we should also explore the idea of using bazel RBE as the Linux CI does to cut down build times etc. Other projects (namely gRPC and tensorflow) seem to have success with this in their CI.
Questions:
envoy-build-tools
repo + setting up a toolchain? etc.)Links:
cl.exe
: https://dev.azure.com/cncf/envoy/_build/results?buildId=36492&view=logs&jobId=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=168f295b-0553-5364-35f7-923225ecd8b3The text was updated successfully, but these errors were encountered: