commit | b83b48c8d4e43546f69d5b5bd79031ab25c179ee | [log] [tgz] |
---|---|---|
author | Xdng Yng <wyverald@gmail.com> | Mon Apr 22 07:45:50 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 22 07:47:41 2024 -0700 |
tree | 6a159450cd0803974f5c75906fe2ec536d22b54d | |
parent | 64f6169732f6b71d85edabbad6be70881754a1ad [diff] |
Add a new `include()` directive to MODULE.bazel files This new directive allows the root module to divide its `MODULE.bazel` into multiple segments. This directive can only be used by root modules; only files in the main repo may be included; variable bindings are only visible in the file they occur in, not in any included or including files. See the docs for `include()` (in `ModuleFileGlobals.java`) for more details. In follow-ups, we'll need to address: 1. Enforcing the loaded files to have some sort of naming format (tentatively `foo.MODULE.bazel` where `foo` is anything) 2. Making `bazel mod tidy` work with included files RELNOTES: Added a new `include()` directive to `MODULE.bazel` files. Fixes https://github.com/bazelbuild/bazel/issues/17880. Closes #21855. PiperOrigin-RevId: 627034184 Change-Id: Ifc2f616cf0791445daeeac9ca5ec4478e83382aa
{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