commit | b20d28194fc0e8d6feb3d541691454c55bfbdc29 | [log] [tgz] |
---|---|---|
author | Googler <arostovtsev@google.com> | Thu Nov 14 10:57:49 2024 -0800 |
committer | keertk <keerthanakumar@google.com> | Tue Nov 19 18:05:59 2024 +0000 |
tree | e51bcadd55e51de6fc9903899fe87e7621b4eb29 | |
parent | 127931cb8f456c09b3d3521611cb28a9b845010d [diff] |
Put macro attribute inheritance behind an off-by-default --experimental_enable_macro_inherit_attrs flag We still have open questions about how macro attribute inheritance ought to interact with the tracking of whether rule attributes were or were not explicitly provided. In effect, this re-opens https://github.com/bazelbuild/bazel/issues/24066 Part of addressing https://github.com/bazelbuild/bazel/issues/24319 RELNOTES: symbolic macro attribute inheritance is now marked experimental; set --experimental_enable_macro_inherit_attrs flag to enable it. PiperOrigin-RevId: 696582223 Change-Id: I3d7cb434bf8fe2da9cd10019e6075990205e7153
{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