| commit | 651be7132eaa0faaedf121c33ea5d6e96d227160 | [log] [tgz] |
|---|---|---|
| author | Googler <lberki@google.com> | Tue Feb 13 07:21:32 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 13 07:22:34 2024 -0800 |
| tree | 501c5540b032671d98f28bdfa3ffc180849d8d65 | |
| parent | 794ead98f17d85ae79784c975308670eef1cc641 [diff] |
Make it possible to override the path of runfiles trees. This is needed for a quirk in the remote execution implementation at Google. Previously, its implementation was in Google-internal code but removing RunfilesSupplier requires that we move this code here. It's quite a bit of of boilerplate, but in exchange we can delete RunfilesSupplier.getRunfilesDirOverride() and remove the "possibly incorrect" path from getPossiblyIncorrectExecPath(). This also encapsulates knowledge about the runfiles trees in InputMetadataProvider, where it belongs. RELNOTES: None. PiperOrigin-RevId: 606613420 Change-Id: I4d9220ba02758a100f7115b2f3a5995c4c3e4ac4
{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
