| commit | e3f319e19dc4e828c78b76cab8aaea3f38b488e8 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Jun 09 16:09:11 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 09 16:10:23 2022 -0700 |
| tree | 08efe9cfd2dcbe098467f482b17b5e8f7f33b47a | |
| parent | 03e9b7d15c9bde4ca4cfca5ddb8acdcabb5732b5 [diff] |
labels in genquery.scope are no longer configured. genquery is all about loading phase concepts, so there is no reason why building a `genquery` rule under configuration X should result in the scope being configured. This is done by introducing a new BuildType.GENQUERY_SCOPE_TYPE_LIST, which represents a dependency, which is followed in the loading phase (so incrementality is not affected) but is NOT followed in the analysis phase (so it does not need to be configured). RELNOTES: labels in genquery.scope are no longer configured. PiperOrigin-RevId: 454035034 Change-Id: I08b2c588565cbed84af9fe33aee121e12892f293
{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
