mirror of
https://github.com/angular/angular-cli.git
synced 2025-04-20 13:31:44 +08:00
170 lines
6.6 KiB
Plaintext
170 lines
6.6 KiB
Plaintext
# Disable NG CLI TTY mode
|
|
build --action_env=NG_FORCE_TTY=false
|
|
|
|
# Make TypeScript compilation fast, by keeping a few copies of the compiler
|
|
# running as daemons, and cache SourceFile AST's to reduce parse time.
|
|
build --strategy=TypeScriptCompile=worker
|
|
|
|
# Enable debugging tests with --config=debug
|
|
test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results
|
|
|
|
# Enable debugging tests with --config=no-sharding
|
|
# The below is useful to while using `fit` and `fdescribe` to avoid sharing and re-runs of failed flaky tests.
|
|
test:no-sharding --flaky_test_attempts=1 --test_sharding_strategy=disabled
|
|
|
|
###############################
|
|
# Filesystem interactions #
|
|
###############################
|
|
|
|
# Create symlinks in the project:
|
|
# - dist/bin for outputs
|
|
# - dist/testlogs, dist/genfiles
|
|
# - bazel-out
|
|
# NB: bazel-out should be excluded from the editor configuration.
|
|
# The checked-in /.vscode/settings.json does this for VSCode.
|
|
# Other editors may require manual config to ignore this directory.
|
|
# In the past, we saw a problem where VSCode traversed a massive tree, opening file handles and
|
|
# eventually a surprising failure with auto-discovery of the C++ toolchain in
|
|
# MacOS High Sierra.
|
|
# See https://github.com/bazelbuild/bazel/issues/4603
|
|
build --symlink_prefix=dist/
|
|
|
|
# Disable watchfs as it causes tests to be flaky on Windows
|
|
# https://github.com/angular/angular/issues/29541
|
|
build --nowatchfs
|
|
|
|
# Turn off legacy external runfiles
|
|
run --nolegacy_external_runfiles
|
|
test --nolegacy_external_runfiles
|
|
|
|
# Turn on --incompatible_strict_action_env which was on by default
|
|
# in Bazel 0.21.0 but turned off again in 0.22.0. Follow
|
|
# https://github.com/bazelbuild/bazel/issues/7026 for more details.
|
|
# This flag is needed to so that the bazel cache is not invalidated
|
|
# when running bazel via `yarn bazel`.
|
|
# See https://github.com/angular/angular/issues/27514.
|
|
build --incompatible_strict_action_env
|
|
run --incompatible_strict_action_env
|
|
test --incompatible_strict_action_env
|
|
|
|
# Enable remote caching of build/action tree
|
|
build --experimental_remote_merkle_tree_cache
|
|
|
|
# Ensure that tags applied in BUILDs propagate to actions
|
|
build --incompatible_allow_tags_propagation
|
|
|
|
# Don't check if output files have been modified
|
|
build --noexperimental_check_output_files
|
|
|
|
# Ensure sandboxing is enabled even for exclusive tests
|
|
test --incompatible_exclusive_test_sandboxed
|
|
|
|
###############################
|
|
# Saucelabs support #
|
|
# Turn on these settings with #
|
|
# --config=saucelabs #
|
|
###############################
|
|
|
|
# Expose SauceLabs environment to actions
|
|
# These environment variables are needed by
|
|
# web_test_karma to run on Saucelabs
|
|
test:saucelabs --action_env=SAUCE_USERNAME
|
|
test:saucelabs --action_env=SAUCE_ACCESS_KEY
|
|
test:saucelabs --action_env=SAUCE_READY_FILE
|
|
test:saucelabs --action_env=SAUCE_PID_FILE
|
|
test:saucelabs --action_env=SAUCE_TUNNEL_IDENTIFIER
|
|
test:saucelabs --define=KARMA_WEB_TEST_MODE=SL_REQUIRED
|
|
|
|
###############################
|
|
# Release support #
|
|
# Turn on these settings with #
|
|
# --config=release #
|
|
###############################
|
|
|
|
# Releases should always be stamped with version control info
|
|
# This command assumes node on the path and is a workaround for
|
|
# https://github.com/bazelbuild/bazel/issues/4802
|
|
build:release --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=release"
|
|
build:release --stamp
|
|
|
|
build:snapshot --workspace_status_command="yarn -s ng-dev release build-env-stamp --mode=snapshot"
|
|
build:snapshot --stamp
|
|
build:snapshot --//:enable_snapshot_repo_deps
|
|
|
|
build:local --//:enable_package_json_tar_deps
|
|
|
|
###############################
|
|
# Output #
|
|
###############################
|
|
|
|
# A more useful default output mode for bazel query
|
|
# Prints eg. "ng_module rule //foo:bar" rather than just "//foo:bar"
|
|
query --output=label_kind
|
|
|
|
# By default, failing tests don't print any output, it goes to the log file
|
|
test --test_output=errors
|
|
|
|
################################
|
|
# Settings for CircleCI #
|
|
################################
|
|
|
|
# Bazel flags for CircleCI are in /.circleci/bazel.rc
|
|
|
|
################################
|
|
# Remote Execution Setup #
|
|
################################
|
|
|
|
# Use the Angular team internal GCP instance for remote execution.
|
|
build:remote --remote_instance_name=projects/internal-200822/instances/primary_instance
|
|
build:remote --bes_instance_name=internal-200822
|
|
|
|
# Starting with Bazel 0.27.0 strategies do not need to be explicitly
|
|
# defined. See https://github.com/bazelbuild/bazel/issues/7480
|
|
build:remote --define=EXECUTOR=remote
|
|
|
|
# Setup the remote build execution servers.
|
|
build:remote --remote_cache=remotebuildexecution.googleapis.com
|
|
build:remote --remote_executor=remotebuildexecution.googleapis.com
|
|
build:remote --remote_timeout=600
|
|
build:remote --jobs=150
|
|
|
|
# Setup the toolchain and platform for the remote build execution. The platform
|
|
# is provided by the shared dev-infra package and targets k8 remote containers.
|
|
build:remote --crosstool_top=@npm//@angular/build-tooling/bazel/remote-execution/cpp:cc_toolchain_suite
|
|
build:remote --extra_toolchains=@npm//@angular/build-tooling/bazel/remote-execution/cpp:cc_toolchain
|
|
build:remote --extra_execution_platforms=@npm//@angular/build-tooling/bazel/remote-execution:platform_with_network
|
|
build:remote --host_platform=@npm//@angular/build-tooling/bazel/remote-execution:platform_with_network
|
|
build:remote --platforms=@npm//@angular/build-tooling/bazel/remote-execution:platform_with_network
|
|
|
|
# Set remote caching settings
|
|
build:remote --remote_accept_cached=true
|
|
|
|
# Force remote executions to consider the entire run as linux.
|
|
# This is required for OSX cross-platform RBE.
|
|
build:remote --cpu=k8
|
|
build:remote --host_cpu=k8
|
|
|
|
# Set up authentication mechanism for RBE
|
|
build:remote --google_default_credentials
|
|
|
|
###############################
|
|
# NodeJS rules settings
|
|
# These settings are required for rules_nodejs
|
|
###############################
|
|
|
|
# Fixes use of npm paths with spaces such as some within the puppeteer module
|
|
build --experimental_inprocess_symlink_creation
|
|
|
|
####################################################
|
|
# User bazel configuration
|
|
# NOTE: This needs to be the *last* entry in the config.
|
|
####################################################
|
|
|
|
# Load any settings which are specific to the current user. Needs to be *last* statement
|
|
# in this config, as the user configuration should be able to overwrite flags from this file.
|
|
try-import .bazelrc.user
|
|
|
|
# Enable runfiles even on Windows.
|
|
# Architect resolves output files from data files, and this isn't possible without runfile support.
|
|
build --enable_runfiles
|