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

27 lines
1.1 KiB
Plaintext
Raw Normal View History

ci: enable bazel remote caching on CircleCI (#21784) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784
2018-01-25 12:55:27 -05:00
# These options are enabled when running on CI
# We do this by copying this file to /etc/bazel.bazelrc at the start of the build.
build: update to Bazel 0.20 (#27394) refactor Bazel RBE configs PR Close #27394
2018-12-01 19:08:15 -05:00
# See documentation in /docs/BAZEL.md
ci: enable bazel remote caching on CircleCI (#21784) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784
2018-01-25 12:55:27 -05:00
# Don't be spammy in the logs
build(bazel): show bazel progress in CircleCI to prevent 10m timeout with no output (#24663) PR Close #24663
2018-07-13 20:27:36 -04:00
# TODO(gmagolan): Hide progress again once build performance improves
# Presently, CircleCI can timeout during bazel test ... with the following
# error: Too long with no output (exceeded 10m0s)
# build --noshow_progress
ci: enable bazel remote caching on CircleCI (#21784) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784
2018-01-25 12:55:27 -05:00
build: flatten esm5 sources before rollup (#23131) this is needed to update to latest rules_nodejs due to breaking change in https://github.com/bazelbuild/rules_nodejs/pull/172 It has the side-effect of correctly marking rxjs packages as side-effect-free PR Close #23131
2018-04-02 19:34:48 -04:00
# Print all the options that apply to the build.
# This helps us diagnose which options override others
# (e.g. /etc/bazel.bazelrc vs. tools/bazel.rc)
build --announce_rc
ci: enable bazel remote caching on CircleCI (#21784) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784
2018-01-25 12:55:27 -05:00
# Workaround https://github.com/bazelbuild/bazel/issues/3645
# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
ci: double our cores on CircleCI (#22641) This should cut our build time in ~half, assuming it's widely parallel. See https://circleci.com/docs/2.0/configuration-reference/#resource_class Also enable bazel repository caching, and store the external repositories in the CircleCI cache for later builds. PR Close #22641
2018-03-07 20:26:03 -05:00
# Limit Bazel to consuming resources that fit in CircleCI "xlarge" class
ci: enable bazel remote caching on CircleCI (#21784) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784
2018-01-25 12:55:27 -05:00
# https://circleci.com/docs/2.0/configuration-reference/#resource_class
ci: double our cores on CircleCI (#22641) This should cut our build time in ~half, assuming it's widely parallel. See https://circleci.com/docs/2.0/configuration-reference/#resource_class Also enable bazel repository caching, and store the external repositories in the CircleCI cache for later builds. PR Close #22641
2018-03-07 20:26:03 -05:00
build --local_resources=14336,8.0,1.0
ci: enable bazel remote caching on CircleCI (#21784) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784
2018-01-25 12:55:27 -05:00
# Retry in the event of flakes, eg. https://circleci.com/gh/angular/angular/31309
test --flaky_test_attempts=2
test(bazel): Run Angular test on RBE (#25370) PR Close #25370
2018-08-02 00:02:36 -04:00
# More details on failures
build --verbose_failures=true