ci: manually set available resources for bazel on windows CI (#36458)

PR Close #36458
This commit is contained in:
Joey Perrott 2020-04-06 12:15:05 -07:00 committed by Kara Erickson
parent d2623f13d9
commit 2dd6f25647
2 changed files with 6 additions and 1 deletions

View File

@ -14,7 +14,8 @@ build --repository_cache=/home/circleci/bazel_repository_cache
# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
# https://circleci.com/docs/2.0/configuration-reference/#resource_class
build --local_resources=14336,8.0,1.0
build --local_cpu_resources=8
build --local_ram_resources=14336
# All build executed remotely should be done using our RBE configuration.
build:remote --google_default_credentials

View File

@ -10,6 +10,10 @@ try-import %workspace%/.circleci/bazel.common.rc
# speeding up the analysis time significantly with Bazel managed node dependencies on the CI.
build --repository_cache=C:/Users/circleci/bazel_repository_cache
# Manually set the local resources used in windows CI runs
build --local_ram_resources=13500
build --local_cpu_resources=4
# 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