| commit | c4991038391a9634b0978f7a20665a3aa9877bf3 | [log] [tgz] |
|---|---|---|
| author | wyv <wyv@google.com> | Tue May 24 06:13:55 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 24 06:15:12 2022 -0700 |
| tree | d28003600e6971ce4e28efd6d15fa60197e33a53 | |
| parent | 5d936d48b07b033cf6388a16f6639886ef87f514 [diff] |
Bzlmod: Proper repo mappings for @_builtins @_builtins is not a real repo and does not currently have repo mappings. However, things in there still sometimes use things from other repos (eg. @platforms). This isn't a problem pre-Bzlmod since @platforms is just called @platforms, but in Bzlmod it's called @platforms.0.0.4, so things break. This CL changes it so that when Bzlmod is enabled, @_builtins adopts the repo mapping of @bazel_tools, the built-in module. Note that the repo mapping of @bazel_tools does not have a dependency on the //external package, so there is still no circular SkyValue dependency. Fixes https://github.com/bazelbuild/bazel/issues/15317. PiperOrigin-RevId: 450665054
{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
