| commit | c00c272097c151344be3aeb530abb4f074fa2a23 | [log] [tgz] |
|---|---|---|
| author | Googler <ilist@google.com> | Thu Nov 16 02:46:02 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 16 02:47:32 2023 -0800 |
| tree | 5dc001e9af657f6104ab81a63673babd7f776393 | |
| parent | 191ad1efa060883fa786d9f5d97f395a27fdcad5 [diff] |
Cleanup incoming configuration transitions on Starlark rules Remove PatchTransition and TransitionFactory. Those don't seem to be possible inputs in Starlark, because they don't implement StarlarkValue, with exception of ExecTransitionFactory. Using exec as an incoming transition seems like a really weird use case, and it's probably better not to support it, than making Bazel code more complex. There seem to be no uses of exec incoming transition on github: https://github.com/search?q=%22cfg+%3D+config%22+language%3AStarlark&type=repositories&ref=advsearch Remove RuleClass.cfg(PatchTransition). It was only used in tests. Inline the uses. Add Nullable to RuleClass.transitionFactory. This is preparation to support cfg on extended rules. RELNOTES[INC]: Incoming transitions on rules can't be set to "exec" transition. PiperOrigin-RevId: 582969396 Change-Id: I1e6391d17671fdfa60e1945561396107172c6a4a
{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
