Download cached source directories in the runfiles of top-level targets (#31473) ### Description The files below a source directory of a repo that has been retrieved from the remote repo contents cache are only downloaded when the directory is requested from the prefetcher. For the runfiles of a top-level target, only artifacts with remote metadata were requested, which a source directory doesn't have. Source directories in external repos are now requested as well if they are selected for download. ### Motivation With a source directory of a cached repo in the runfiles of a binary, `bazel run` ran the binary without the directory in its runfiles tree. Work towards #31456 ### Build API Changes No ### Release Notes RELNOTES: None Closes #31473 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/31473 from fmeum:rrcc-run-source-directories 99e1973eee3e244b8e44e7191c63822c55f78f52 PiperOrigin-RevId: 999899308 Change-Id: I72c3806cc741f20d19b3aaeeb0202ef8c49de322
{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.
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
