| commit | 62582bd74d2a154e94a9e1e64fcbeeae22fbf88c | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Mon Oct 18 04:41:16 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 18 04:42:31 2021 -0700 |
| tree | 909933854c4f60c301c3e6f8aa43b0178fbdc7f7 | |
| parent | b35944e4fedbfa65a7b081021959584ab9a07a84 [diff] |
Retain runfiles when forwarding DelegatingDefaultInfo Before this change, returning a DefaultInfo obtained from a native rule target from a Starlark rule would lose the data_runfiles and default_runfiles. This could only be worked around by creating a DefaultInfo provider instance in Starlark explicitly setting these fields. This is fixed by having the DelegatingDefaultInfo return null instead of an empty Runfiles object for the stateless runfiles, which indicates to addSimpleProviders in StarlarkRuleConfiguredTargetUtils that default and data runfiles should be used instead. Previously, this logic would only use the always empty stateless runfiles. Fixes #9442. Closes #14123. PiperOrigin-RevId: 403921510
{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
