forked from mattem/rules_nodejs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.bazelrc
36 lines (28 loc) · 1.46 KB
/
.bazelrc
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# Import shared settings first so we can override below
import %workspace%/common.bazelrc
# Mock versioning command to test the --stamp behavior
build --workspace_status_command="echo BUILD_SCM_VERSION 1.2.3"
# ... but when releasing, use the real script instead
build:release --workspace_status_command=./scripts/current_version.sh
# Avoid python 3 which requires explicit toolchain config
# This is needed only for the pkg_tar rule
build --host_force_python=PY2
# Opt-in to upcoming breaking changes
build --incompatible_disable_legacy_proto_provider
build --incompatible_use_python_toolchains
common --incompatible_string_join_requires_strings
# TODO(gregmagolan): remove the following flags once @io_bazel_rules_go is compatible with Bazel 0.27.0
build --noincompatible_require_ctx_in_configure_features
build --noincompatible_no_support_tools_in_action_inputs
# Define environment value used by some tests such as //internal/npm_install/test:bazel_bin_test
test --define=SOME_TEST_ENV=some_value
###############################
# Remote Build Execution support
# Turn on these settings with
# --config=remote
###############################
# Load default settings for Remote Build Execution.
import %workspace%/third_party/github.com/bazelbuild/bazel-toolchains/bazelrc/bazel-0.28.0.bazelrc
# Remote instance, borrow the one used by Angular devs
build:remote --remote_instance_name=projects/internal-200822/instances/default_instance
build:remote --project_id=internal-200822