| commit | 9cb59369a84d9328c2929eefcb58c1b972ab15f2 | [log] [tgz] |
|---|---|---|
| author | pcloudy <pcloudy@google.com> | Mon Sep 06 09:24:20 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Sep 06 09:25:54 2021 -0700 |
| tree | 456ca9e0fcfd590a5edb97d663002e90d80a56e6 | |
| parent | 11f7d8040fadc595589ee264561606dc2a83685d [diff] |
bzlmod: Enforce strict deps for Bzlmod generated repos ================================================================= Bzlmod generated repos can only access repos of its declared direct dependencies. To implement this, new attribute containing information about the owner repo is added to `RepositoryMapping` and `RepositoryName`. * In `RepositoryMapping`, if `ownerRepo` is not null, then it means strict dependency is enforced. * In `RepositoryName`, if `ownerRepoIfInvisible` is not null, then it means the repository name is actually not visible after repo mapping and should fail in `RepositoryDelegatorFunction` when trying to fetch the repository. Working towards: https://github.com/bazelbuild/bazel/issues/13793 Related: https://github.com/bazelbuild/bazel/issues/13316 RELNOTES: None PiperOrigin-RevId: 395109190
{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
