| commit | 2a8ab5bd774a9e7023a933efb1b64a0f1cce5ba3 | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Fri Mar 10 08:20:47 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 10 08:22:39 2023 -0800 |
| tree | 7979bc4874d08a961c6e9bdcfaf9ad2f963acaaa | |
| parent | 6fc9171867ad38cf91b814881a49d0f6a3f0fb3a [diff] |
Implement MetadataProvider in RemoteActionFileSystem. This makes it possible (in a followup change) to delete the downloadFile() prefetcher method in favor of prefetchFiles(). When the action filesystem implements MetadataProvider, Skyframe considers it the authoritative source for input metadata [1]. Therefore, getInput() and getMetadata() need to look in all of the right places (the action input map, the output mapping, the remote output tree, and the local filesystem) and get all of the combinations of source/output and local/remote right. [1] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/skyframe/SkyframeActionExecutor.java;l=859;drc=9f8395661b2a74299cf01b1a1cdd04cc4f25dcf0 PiperOrigin-RevId: 515642065 Change-Id: I62caf3aafa4acc23f70cc4511997335e82ebb12a
{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
