No longer allow exceptions to action conflict checking. Before, we did not allow two output artifacts in the same build to prefix each other, eg "out/foo/bar" and "out/foo" could not both be represented. Unfortunately, there were unintentional exceptions for such conflicts within a single action, which I believe date back to olden times when not all actions ran remotely and Blaze actions themselves were not as nicely behaved. In modern times, this can happen when a Starlark action creates a tree artifact and a file artifact underneath the tree. This is really strange (what should a downstream action that depends on the tree artifact see?). Forbid such a construct. RELNOTES[INC]: Tree artifacts and regular artifact paths can no longer overlap. PiperOrigin-RevId: 277098529
{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:
See CONTRIBUTING.md
