| commit | ca1c3370e5ed57dbf79f5b61a7292e4c79ffdcbf | [log] [tgz] |
|---|---|---|
| author | Googler <gregce@google.com> | Mon Oct 23 08:51:51 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 23 08:53:28 2023 -0700 |
| tree | c634b656354d90b41e83b17702e7fbd23809336f | |
| parent | e692745f3b42c48bb460a52231a3978a7b9192d7 [diff] |
Support Starlark exec transitions for all code paths. Before this change, production code supported `--experimental_starlark_exec`. But some test code and `BaselineOptionsFunction` didn't. This change opts them in too. ### Details: - `AnalysisTestUtil` has an exec config getter that completely ignores the Starlark transition: when it sets up `ExecutionTransitionFactory`'s `AttributeTransitionData`, it omits the `analysisData` setter that injects the Starlark transition. - I added that setter. But since this isn't a Skyfunction, I had to refactor the transition loading logic. I moved it to a dedicated class (`StarlarkExecTransitionLoader`) and added access points for all relevant callers. - `StarlarkExecTransitionLoader` is just a copy of what was previously in `DependencyResolver`. PiperOrigin-RevId: 575831770 Change-Id: I16889d111e4a1c0304629c4de870cdee1976a4c5
{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
