Add --experimental_exec_configuration_distinguisher This work is cleaved off from the --experimental_output_directory_naming_scheme work (see https://github.com/bazelbuild/bazel/issues/14023) and is meant as a less-exotic (and more quickly deployable) way to fix-up potential action conflicts due to insufficient configuration distinguishing in or around the exec transition. The following modes are added: legacy: Keep current behavior of only setting platform_suffix to exec-%X where %X is a hash of the current execution platform. fullHash: Set platform_suffix to exec-%X where %X is a hash of the entire post-configuration transition (although, with platform_suffix emptied, to prevent self-referential hashing headaches). diffToAffected: Set platform_suffix to exec (only for ease in reading output paths) and update `affected by Starlark transition` with all changed options. This effectively treats the exec transition like a Starlark transition. off: Do not touch platform_suffix or do any other work inside the execution transition to ensure distinguished configurations. This is expected to be used with --experimental_output_directory_naming_scheme as part of removing these local configuration distinguishers in favor of a global system. PiperOrigin-RevId: 433839227
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
