| commit | c8116b166cc09e1607db437ed4395a3153b45629 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed May 18 15:16:54 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 18 15:18:50 2022 -0700 |
| tree | 1e00b4cb9b82d37deae7d80fc83b9a1c413fae4c | |
| parent | f068b31c94eef1ea10477a755d9173b4fadf6485 [diff] |
Explicitly mention that `alias()` ignores `testonly`. This is to make clear that testonly is ignored to prevent accidental misuse which is otherwise hard to detect. Exposing a testonly alias is an appealing option when the non-testonly target is visibility-restricted, but usage from arbitrary tests is acceptable (e.g., a fake/no-op implementation of an authentication/authorization library could freely be used by any test, but the underlying, non-testonly, library uses visibility so that only vetted/trusted users can use it). PiperOrigin-RevId: 449589636
{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
