| commit | 208a728f46c72afc592e731d870c1b6606ec9406 | [log] [tgz] |
|---|---|---|
| author | Googler <gregce@google.com> | Mon Nov 20 11:14:28 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 20 11:15:43 2023 -0800 |
| tree | 956ead98458969952a1f0878955db0bc68d7835e | |
| parent | faa2f3d6a1a660fa2f13e9a119dc26d69d358d90 [diff] |
Enable Starlark exec transition in code paths that weren't setting it. Bazel injects the Starlark transition by setting [analysisData](https://github.com/bazelbuild/bazel/blob/ca84e545b513043204c09bca66a9ffcbc922e2c7/src/main/java/com/google/devtools/build/lib/packages/AttributeTransitionData.java#L46) on `AttributeTransitionData`, then passing `AttributeTransitionData` to parameterize `ExecutionTransitionFactory`. [Example](https://github.com/bazelbuild/bazel/blob/ca84e545b513043204c09bca66a9ffcbc922e2c7/src/main/java/com/google/devtools/build/lib/analysis/producers/DependencyProducer.java#L153-L156). The main configuration code path does this. But there are a few other code paths for production & testing corner cases that also need to opt in. PiperOrigin-RevId: 584078882 Change-Id: Ie560a94b179aff906dc3fc7bd806f57dc1b0b300
{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
