honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ci: use larger resource classes for bazel builds (#39124) 

Migrates to using larger resource classes for windows CI runs as well as updating
the bazel rcs for windows and linux to use all/more of the resources available in
the executors

PR Close #39124
This commit is contained in:
Joey Perrott 2020-10-05 15:46:36 -07:00
parent d8c05347c3
commit ee03408c44
4 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.circleci/bazel.linux.rc
View File

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

4
.circleci/bazel.windows.rc
View File

@ -11,8 +11,8 @@ try-import %workspace%/.circleci/bazel.common.rc
build --repository_cache=C:/Users/circleci/bazel_repository_cache build --repository_cache=C:/Users/circleci/bazel_repository_cache
# Manually set the local resources used in windows CI runs # Manually set the local resources used in windows CI runs
build --local_ram_resources=13500 build --local_ram_resources=120000
build --local_cpu_resources=4 build --local_cpu_resources=32
# All windows jobs run on master and should use http caching # All windows jobs run on master and should use http caching
build --remote_http_cache=https://storage.googleapis.com/angular-team-cache build --remote_http_cache=https://storage.googleapis.com/angular-team-cache

2
.circleci/config.yml
View File

@ -80,7 +80,7 @@ executors:
windows-executor: windows-executor:
working_directory: ~/ng working_directory: ~/ng
resource_class: windows.medium resource_class: windows.2xlarge
# CircleCI windows VMs do have the GitBash shell available: # CircleCI windows VMs do have the GitBash shell available:
# https://github.com/CircleCI-Public/windows-preview-docs#shells # https://github.com/CircleCI-Public/windows-preview-docs#shells
# But in this specific case we really should not use it because Bazel must not be ran from # But in this specific case we really should not use it because Bazel must not be ran from

3
.circleci/windows-env.ps1
View File

@ -41,7 +41,8 @@ copy .circleci\bazel.windows.rc ${Env:USERPROFILE}\.bazelrc
#################################################################################################### ####################################################################################################
# Install specific version of node. # Install specific version of node.
#################################################################################################### ####################################################################################################
choco install nodejs --version 12.14.1 --no-progress nvm install 12.14.1
nvm use 12.14.1
# These Bazel prereqs aren't needed because the CircleCI image already includes them. # These Bazel prereqs aren't needed because the CircleCI image already includes them.
# choco install yarn --version 1.16.0 --no-progress # choco install yarn --version 1.16.0 --no-progress