From 2dd6f25647c0c9e74401af7d1da7489a03f7e5ba Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Mon, 6 Apr 2020 12:15:05 -0700 Subject: [PATCH] ci: manually set available resources for bazel on windows CI (#36458) PR Close #36458 --- .circleci/bazel.linux.rc | 3 ++- .circleci/bazel.windows.rc | 4 ++++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/.circleci/bazel.linux.rc b/.circleci/bazel.linux.rc index 4889f934b2..afb8fd47f1 100644 --- a/.circleci/bazel.linux.rc +++ b/.circleci/bazel.linux.rc @@ -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 diff --git a/.circleci/bazel.windows.rc b/.circleci/bazel.windows.rc index 9efa954554..ce3e53392c 100644 --- a/.circleci/bazel.windows.rc +++ b/.circleci/bazel.windows.rc @@ -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