ef665889a1
Since we always execute our bazel commands using RBE on CI we should not have separete tasks of configuring bazel and setting up RBE for bazel. Enabling RBE for bazel should be part of our bazel configuration process on CI. PR Close #34834
18 lines
876 B
Plaintext
18 lines
876 B
Plaintext
# These options are enabled when running on CI
|
|
# We do this by copying this file to $env:ProgramData\bazel.bazelrc at the start of the build.
|
|
# See documentation in /docs/BAZEL.md
|
|
|
|
# Import config items common to both Linux and Windows setups.
|
|
# https://docs.bazel.build/versions/master/guide.html#bazelrc-syntax-and-semantics
|
|
try-import %workspace%/.circleci/bazel.common.rc
|
|
|
|
# Save downloaded repositories in a location that can be cached by CircleCI. This helps us
|
|
# speeding up the analysis time significantly with Bazel managed node dependencies on the CI.
|
|
build --repository_cache=C:/Users/circleci/bazel_repository_cache
|
|
|
|
# All windows jobs run on master and should use http caching
|
|
build --remote_http_cache=https://storage.googleapis.com/angular-team-cache
|
|
build --remote_accept_cached=true
|
|
build --remote_upload_local_results=true
|
|
build --google_default_credentials
|