ci: enable the Windows Bazel workflow path

This commit is contained in:
Michael Bolin
2026-03-26 23:10:45 -07:00
parent 41fe98b185
commit 66dfd10d45
7 changed files with 211 additions and 14 deletions
+9 -2
View File
@@ -20,8 +20,9 @@ common:windows --host_platform=//:local_windows
common --@rules_cc//cc/toolchains/args/archiver_flags:use_libtool_on_macos=False
common --@llvm//config:experimental_stub_libgcc_s
# We need to use the sh toolchain on windows so we don't send host bash paths to the linux executor.
common:windows --@rules_rust//rust/settings:experimental_use_sh_toolchain_for_bootstrap_process_wrapper
# `rules_rs` no longer exposes this `rules_rust` setting, so keep Windows on the
# default bootstrap process wrapper path until the workflow is green again.
# common:windows --@rules_rust//rust/settings:experimental_use_sh_toolchain_for_bootstrap_process_wrapper
# TODO(zbarsky): rules_rust doesn't implement this flag properly with remote exec...
# common --@rules_rust//rust/settings:pipelined_compilation
@@ -80,6 +81,12 @@ common:ci-windows --config=ci-bazel
common:ci-windows --build_metadata=TAG_os=windows
common:ci-windows --repo_contents_cache=D:/a/.cache/bazel-repo-contents-cache
common:ci-windows --repository_cache=D:/a/.cache/bazel-repo-cache
# llvm-mingw in the gnullvm toolchain does not ship libssp_nonshared, so the
# default stack protector flags from rules_cc break C/C++ build scripts such as
# aws-lc-sys. Override them for this Windows CI path until the toolchain setup
# is fixed more centrally.
common:ci-windows --copt=-fno-stack-protector
common:ci-windows --host_copt=-fno-stack-protector
# We prefer to run the build actions entirely remotely so we can dial up the concurrency.
# We have platform-specific tests, so we want to execute the tests on all platforms using the strongest sandboxing available on each platform.