Check for duplicates labels in multi-select statements after analysis. Checking for duplicates in labels in the load phase results can reulst in false positives where there is no duplicate for any particular configuration but the same file is referenced in multiple select statements. For label lists without a select or those that only have a single select, the check remains in the loading phase. For label lists with multiple selects, the check occurs after configurations are resolved and only checks for duplicate labels in the configurations used within a build rather than all potential configurations. RELNOTES: selects() no longer produce irrelevant duplicate label checks PiperOrigin-RevId: 470241662 Change-Id: I626518b96a66cc1fd80b8d355dbfd69506c061a9
{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
