| commit | a0e0dc5326ba2d77d36034b2916b25617d1a565c | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Oct 03 11:41:28 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 03 11:42:48 2023 -0700 |
| tree | cf10d7585b6a5835b3a66169b9e4475426b28f30 | |
| parent | 4647633bf6f6eb05de2b30b749ad63902a9f1b1f [diff] |
After https://github.com/bazelbuild/bazel/commit/ceddfb1ece1f8ed7ff81558fa1751e6526df031b, select statements are evaluated before computing and applying rule transition. As discovered, this can lead to issues when those select statements are not resolvable. Currently, this causes bazel to crash which is undesirable as any unresolvable selects should not stop the transition from being executed. This cl introduces SelectResolutionResult and AttributeResolutionResult which are both @AutoValue or a tagged-union. Each has SUCCESS and FAILURE types that corresponds to successful resolution of select/attribute and failed resolution of select/attribute. A forked method of getAndValidate named getResolvedAttribute is also added. It returns AttributeResolutionResult which is then used in StarlarkRuleTransitionProvider to handle unresolvable selects prior to rule transitions. PiperOrigin-RevId: 570450889 Change-Id: I32e1e6da3110b042c5791886587ae212ddadf673
{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
