| commit | e35c29fe4670c779e8b96133450959eddf2dae5e | [log] [tgz] |
|---|---|---|
| author | Ivo List <ilist@google.com> | Mon Dec 04 19:44:30 2023 +0100 |
| committer | GitHub <noreply@github.com> | Mon Dec 04 19:44:30 2023 +0100 |
| tree | 4442b5a46ca0f07a853f47b7fe596e20cfd5989c | |
| parent | b1d9fa81e0b611ea11c6a98ceb0042c783783339 [diff] |
[7.0.0] Experimental extend rule and subrule functionality (#20429) Following commits were cleanly cherry-picked: e4c7cb6ecb ilist@google.com Support incoming configuration transition in extended rules faa2f3d6a1 ilist@google.com Support subrules in extended rules d70d198e92 ilist@google.com Add an escape hatch for any type attributes in the initializer c00c272097 ilist@google.com Cleanup incoming configuration transitions on Starlark rules 82a469ffc0 ilist@google.com Copy and lift labels in arguments of initializers 6733c1844b ilist@google.com Remove unused OBJECT_LIST type e7a3dabfb6 ilist@google.com Remove unused FILESET_ENTRY label class c95999046a ilist@google.com Implement type checks and label conversion for Starlark values c4f4073aa8 ilist@google.com Move convertFromBuildLangType into BuildType class Additional commit "Define function_transition_allowlist in StarlarkRuleClassFunctionsTest" just fixes the mocking of the the tests.
{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
