| commit | de37930d7d046d1a96f9c0f725cfb99b453204d0 | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Fri Jun 10 07:04:32 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 10 07:05:38 2022 -0700 |
| tree | 2a74fe590f7a50a902a974633c873ea428106bae | |
| parent | e123eaa30341e2c7c52076064074930f8f1dc703 [diff] |
'@'-prefixed canonical repo names for Bzlmod repos See https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDot7bdUsjz6JFC4/edit#heading=h.z37pyziy8h33 * RepositoryName syntax is relaxed to allow an extra '@' in the beginning, signifying that the RepositoryName should bypass RepositoryMapping * All repos generated by Bzlmod will have an extra '@' prefixed to their names (except for well-known modules) * TODO: strip the '@' when generating paths under $outputBase/external or $execRoot/external Work towards https://github.com/bazelbuild/bazel/issues/15593. RELNOTES: When Bzlmod is enabled, all Bzlmod-generated repos will have an extra '@' prepended to their names. This effectively enables the canonical label literal syntax for Bzlmod-generated repos (`@@canonicalRepoName//pkg:target`; see https://docs.google.com/document/d/1N81qfCa8oskCk5LqTW-LNthy6EBrDot7bdUsjz6JFC4/edit?usp=sharing). PiperOrigin-RevId: 454156392 Change-Id: I2fb08495f066cfd15cc344534925f674a63764f6
{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
