41 lines
1.6 KiB
Plaintext
41 lines
1.6 KiB
Plaintext
|
# 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.
|
||
|
|
# See documentation in /docs/BAZEL.md
|
||
|
|
|
||
|
|
# Save downloaded repositories in a location that can be cached by CodeFresh. This helps us
|
||
|
|
# speeding up the analysis time significantly with Bazel managed node dependencies on the CI.
|
||
|
|
# build --repository_cache=C:/codefresh/volume/bazel_repository_cache
|
||
|
|
|
||
|
|
# Don't be spammy in the logs
|
||
|
|
# 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
|
||
|
|
|
||
|
|
# 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
|
||
|
|
|
||
|
|
# Workaround https://github.com/bazelbuild/bazel/issues/3645
|
||
|
|
# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
|
||
|
|
# Limit Bazel to consuming resources that fit in CodeFresh VMs
|
||
|
|
# TODO(filipesilva): determine the correct memory limit
|
||
|
|
build --local_resources=8000,8.0,1.0
|
||
|
|
|
||
|
|
# Retry in the event of flakes, eg. https://circleci.com/gh/angular/angular/31309
|
||
|
|
test --flaky_test_attempts=2
|
||
|
|
|
||
|
|
# More details on failures
|
||
|
|
build --verbose_failures=true
|
||
|
|
|
||
|
|
# Include PATH in Windows build/tests
|
||
|
|
# https://github.com/bazelbuild/rules_typescript/pull/356
|
||
|
|
build --action_env=PATH
|
||
|
|
test --action_env=PATH --test_env=PATH
|
||
|
|
|
||
|
|
# Exclude tests known to not work on Windows.
|
||
|
|
|
||
|
|
# Chrome web tests are currently broken.
|
||
|
|
test --test_tag_filters=-browser:chromium-local
|