b5ec5a7fca
Because the compiler-cli tests modify node_modules, this can cause failures on windows CI specifically as node_modules are symlinked to rather than copied. By running the test and build actions in separate commands, all of the tests are built to be executed before and tests are executed and modify the node_modules content. PR Close #39289
18 lines
750 B
Plaintext
18 lines
750 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
|
|
|
|
# Manually set the local resources used in windows CI runs
|
|
build --local_ram_resources=120000
|
|
build --local_cpu_resources=32
|
|
|
|
# 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
|