# The following flags enable the remote cache so action results can be shared
# across machines, developers, and workspaces.
# 
# This config is loaded from https://github.com/bazelbuild/bazel-toolchains/blob/master/bazelrc/latest.bazelrc
build:remote-cache --remote_cache=remotebuildexecution.googleapis.com
build:remote-cache --tls_enabled=true
build:remote-cache --remote_timeout=3600
build:remote-cache --auth_enabled=true
build:remote-cache --spawn_strategy=standalone
build:remote-cache --strategy=Javac=standalone
build:remote-cache --strategy=Closure=standalone
build:remote-cache --strategy=Genrule=standalone

# Prysm specific remote-cache properties.
build:remote-cache --disk_cache=
build:remote-cache --jobs=50
build:remote-cache --host_platform_remote_properties_override='properties:{name:\"cache-silo-key\" value:\"prysm\"}' 
build:remote-cache --remote_instance_name=projects/prysmaticlabs/instances/default_instance

build --experimental_strict_action_env
build --disk_cache=/tmp/bazelbuilds
build --experimental_multi_threaded_digest
build --sandbox_tmpfs_path=/tmp
build --verbose_failures
build --announce_rc
build --show_progress_rate_limit=5
build --curses=yes --color=yes
build --keep_going
build --test_output=errors
build --flaky_test_attempts=5
build --test_timeout=5,60,-1,-1
# Disabled race detection due to unstable test results under constrained environment build kite
# build --features=race

# Temporary opt-in for rules_nodejs.
build --experimental_allow_incremental_repository_updates

# Workaround for rules_docker.                                                  
# https://github.com/bazelbuild/rules_docker/issues/842                         
build --host_force_python=PY2