################################

# Settings for Angular team members only

################################

# To enable this feature check the "Remote caching" section in docs/BAZEL.md.

build:angular-team --remote_http_cache=https://storage.googleapis.com/angular-team-cache

###############################

# Typescript / Angular / Sass #

###############################

# Make compilation fast, by keeping a few copies of the compilers

# running as daemons, and cache SourceFile AST's to reduce parse time.

build --strategy=AngularTemplateCompile=worker

# TODO(alexeagle): re-enable after fixing worker instability with rxjs typings

# build --strategy=TypeScriptCompile=worker

build --strategy=TypeScriptCompile=standalone

# 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

###############################

# 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 say 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/

# Performance: avoid stat'ing input files

build --watchfs

# 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

###############################

# 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="node ./tools/bazel_stamp_vars.js"

###############################

# 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

# Show which actions are run under workers,

# and print all the actions running in parallel.

# Helps to demonstrate that bazel uses all the cores on the machine.

build --experimental_ui

test --experimental_ui

################################

# Settings for CircleCI #

################################

# Bazel flags for CircleCI are in /.circleci/bazel.rc

################################

# Temporary Settings for Ivy #

################################

# to determine if the compiler used should be Ivy or ViewEngine one can use `--define=compile=aot` on

# any bazel target. This is a temporary flag until codebase is permanently switched to Ivy.

build --define=compile=legacy

###############################

# Remote Build Execution support

# Turn on these settings with

# --config=remote

###############################

# Load default settings for Remote Build Execution

# When updating, the URLs of bazel_toolchains in packages/bazel/package.bzl

# may also need to be updated (see https://github.com/angular/angular/pull/27935)

import %workspace%/third_party/github.com/bazelbuild/bazel-toolchains/bazelrc/bazel-0.21.0.bazelrc

# Increase the default number of jobs by 50% because our build has lots of

# parallelism

build:remote --jobs=150

# Point to our custom execution platform; see tools/BUILD.bazel

build:remote --extra_execution_platforms=//tools:rbe_ubuntu1604-angular

build:remote --host_platform=//tools:rbe_ubuntu1604-angular

build:remote --platforms=//tools:rbe_ubuntu1604-angular

# Remote instance.

build:remote --remote_instance_name=projects/internal-200822/instances/default_instance

# Do not accept remote cache.

# We need to understand the security risks of using prior build artifacts.

build:remote --remote_accept_cached=false

# Load any settings 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