.bazelrc - pigweed/experimental - Git at Google

 # Copyright 2023 The Pigweed Authors
 #
 # Licensed under the Apache License, Version 2.0 (the "License"); you may not
 # use this file except in compliance with the License. You may obtain a copy of
 # the License at
 #
 #     https://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
 # WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
 # License for the specific language governing permissions and limitations under
 # the License.

 # Don't automatically create __init__.py files.
 #
 # This prevents spurious package name collisions at import time, and should be
 # the default (https://github.com/bazelbuild/bazel/issues/7386). It's
 # particularly helpful for Pigweed, because we have many potential package name
 # collisions due to a profusion of stuttering paths like
 # pw_transfer/py/pw_transfer.
 common --incompatible_default_to_explicit_init_py

 # Do not attempt to configure an autodetected (local) toolchain. We vendor all
 # our toolchains, and CI VMs may not have any local toolchain to detect.
 common --repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

 # Required for new toolchain resolution API.
 build --incompatible_enable_cc_toolchain_resolution

 # Don't propagate flags or defines to the exec config. This will become the
 # default one day (https://github.com/bazelbuild/bazel/issues/22457) and will
 # improve cache hit rates between builds targeting different platforms.
 common --experimental_exclude_defines_from_exec_config
 common --experimental_exclude_starlark_flags_from_exec_config

 # Enforces consistent action environment variables. This is important to
 # address Protobuf's rebuild sensitivity on changes to the environment
 # variables. It also improves cache hit rates. Should be true by default one
 # day (https://github.com/bazelbuild/bazel/issues/7026).
 build --incompatible_strict_action_env

 # Expose exec toolchains for Python. We use these toolchains in some rule
 # implementations (git grep for
 # "@rules_python//python:exec_tools_toolchain_type").
 build --@rules_python//python/config_settings:exec_tools_toolchain=enabled

 # Remote execution config definitions
 # ===================================
 # Use the remote cache. This will only work for users who have permission to access it.
 common:remote_cache --bes_backend="buildeventservice.googleapis.com"
 common:remote_cache --bes_instance_name=pigweed-rbe-open
 common:remote_cache --bes_results_url="https://source.cloud.google.com/results/invocations/"
 common:remote_cache --bes_timeout=600s
 common:remote_cache --experimental_remote_cache_eviction_retries=5
 common:remote_cache --google_default_credentials=true
 # Required to use buildeventservice on Bazel 8+.
 # TODO: b/345556899 -- Remove this flag when no longer required.
 common:remote_cache --legacy_important_outputs
 common:remote_cache --remote_cache=grpcs://remotebuildexecution.googleapis.com
 common:remote_cache --remote_instance_name=projects/pigweed-rbe-open/instances/default-instance
 common:remote_cache --remote_upload_local_results=false

 # clang-tidy configuration
 build:clang-tidy --aspects @bazel_clang_tidy//clang_tidy:clang_tidy.bzl%clang_tidy_aspect
 build:clang-tidy --output_groups=report
 build:clang-tidy --@bazel_clang_tidy//:clang_tidy_config=//:clang_tidy_config
 # Use the clang-tidy executable from Pigweed's toolchain, and include
 # our sysroot headers.
 build:clang-tidy --@bazel_clang_tidy//:clang_tidy_executable=@pigweed//pw_toolchain/host_clang:copy_clang_tidy
 build:clang-tidy --@bazel_clang_tidy//:clang_tidy_additional_deps=@pigweed//pw_toolchain/host_clang:sysroot_root
 # Skip any targets with tags = ["noclangtidy"]. This allows a gradual
 # rollout.
 build:clang-tidy --build_tag_filters=-noclangtidy
 # We need to disable this warning to avoid spurious "#pragma once in main file"
 # warnings for header-only libraries. For another approach, see
 # https://github.com/mongodb-forks/bazel_clang_tidy/pull/2
 build:clang-tidy --copt=-Wno-pragma-once-outside-header

 # User bazelrc file; see
 # https://bazel.build/configure/best-practices#bazelrc-file
 #
 # Note: this should be at the bottom of the file, so that user-specified
 # options override anything in this file
 # (https://bazel.build/run/bazelrc#imports)
 try-import %workspace%/user.bazelrc
	# Copyright 2023 The Pigweed Authors
	#
	# Licensed under the Apache License, Version 2.0 (the "License"); you may not
	# use this file except in compliance with the License. You may obtain a copy of
	# the License at
	#
	# https://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software
	# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
	# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
	# License for the specific language governing permissions and limitations under
	# the License.

	# Don't automatically create __init__.py files.
	#
	# This prevents spurious package name collisions at import time, and should be
	# the default (https://github.com/bazelbuild/bazel/issues/7386). It's
	# particularly helpful for Pigweed, because we have many potential package name
	# collisions due to a profusion of stuttering paths like
	# pw_transfer/py/pw_transfer.
	common --incompatible_default_to_explicit_init_py

	# Do not attempt to configure an autodetected (local) toolchain. We vendor all
	# our toolchains, and CI VMs may not have any local toolchain to detect.
	common --repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

	# Required for new toolchain resolution API.
	build --incompatible_enable_cc_toolchain_resolution

	# Don't propagate flags or defines to the exec config. This will become the
	# default one day (https://github.com/bazelbuild/bazel/issues/22457) and will
	# improve cache hit rates between builds targeting different platforms.
	common --experimental_exclude_defines_from_exec_config
	common --experimental_exclude_starlark_flags_from_exec_config

	# Enforces consistent action environment variables. This is important to
	# address Protobuf's rebuild sensitivity on changes to the environment
	# variables. It also improves cache hit rates. Should be true by default one
	# day (https://github.com/bazelbuild/bazel/issues/7026).
	build --incompatible_strict_action_env

	# Expose exec toolchains for Python. We use these toolchains in some rule
	# implementations (git grep for
	# "@rules_python//python:exec_tools_toolchain_type").
	build --@rules_python//python/config_settings:exec_tools_toolchain=enabled

	# Remote execution config definitions
	# ===================================
	# Use the remote cache. This will only work for users who have permission to access it.
	common:remote_cache --bes_backend="buildeventservice.googleapis.com"
	common:remote_cache --bes_instance_name=pigweed-rbe-open
	common:remote_cache --bes_results_url="https://source.cloud.google.com/results/invocations/"
	common:remote_cache --bes_timeout=600s
	common:remote_cache --experimental_remote_cache_eviction_retries=5
	common:remote_cache --google_default_credentials=true
	# Required to use buildeventservice on Bazel 8+.
	# TODO: b/345556899 -- Remove this flag when no longer required.
	common:remote_cache --legacy_important_outputs
	common:remote_cache --remote_cache=grpcs://remotebuildexecution.googleapis.com
	common:remote_cache --remote_instance_name=projects/pigweed-rbe-open/instances/default-instance
	common:remote_cache --remote_upload_local_results=false

	# clang-tidy configuration
	build:clang-tidy --aspects @bazel_clang_tidy//clang_tidy:clang_tidy.bzl%clang_tidy_aspect
	build:clang-tidy --output_groups=report
	build:clang-tidy --@bazel_clang_tidy//:clang_tidy_config=//:clang_tidy_config
	# Use the clang-tidy executable from Pigweed's toolchain, and include
	# our sysroot headers.
	build:clang-tidy --@bazel_clang_tidy//:clang_tidy_executable=@pigweed//pw_toolchain/host_clang:copy_clang_tidy
	build:clang-tidy --@bazel_clang_tidy//:clang_tidy_additional_deps=@pigweed//pw_toolchain/host_clang:sysroot_root
	# Skip any targets with tags = ["noclangtidy"]. This allows a gradual
	# rollout.
	build:clang-tidy --build_tag_filters=-noclangtidy
	# We need to disable this warning to avoid spurious "#pragma once in main file"
	# warnings for header-only libraries. For another approach, see
	# https://github.com/mongodb-forks/bazel_clang_tidy/pull/2
	build:clang-tidy --copt=-Wno-pragma-once-outside-header

	# User bazelrc file; see
	# https://bazel.build/configure/best-practices#bazelrc-file
	#
	# Note: this should be at the bottom of the file, so that user-specified
	# options override anything in this file
	# (https://bazel.build/run/bazelrc#imports)
	try-import %workspace%/user.bazelrc