| commit | 3c1aac19b1fef734fed2450ab3f13d248e90246b | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Wed May 03 09:26:30 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 03 09:27:58 2023 -0700 |
| tree | 612277875caf13e99c04cca00525c476eefb03a3 | |
| parent | 37b8e1b37d5676b3d047b528149546bf2bfefdd1 [diff] |
Remove `CallablePathFragment` class to save memory. `CallablePathFragment` served two purposes: 1. It implemented `PathStrippable` and applied path stripping to derived artifacts. Instead, implement `PathStrippable` directly on `DerivedArtifact`. This works because if path stripping is not enabled for the action, the mapper will be no-op. `PathStrippable` is branched to a top-level interface to avoid a circular dependency. 2. It used `PathFragment#getCallablePathString()` for command line expansion. This method is identical to `Artifact#expandToCommandLine()` so long as the exec path contains a path separator, so it is only expected to make a difference for source artifacts in the root package. Use the `Artifact` itself to save memory if there's no difference. PiperOrigin-RevId: 529111858 Change-Id: Ib7d1d7b168060b0bebc1644914490e8a5bda9783
{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