commit | 44284a95666d5fc71c8436d09d9734349bb8999c | [log] [tgz] |
---|---|---|
author | Googler <jhorvitz@google.com> | Tue Apr 16 09:56:00 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 16 09:58:03 2024 -0700 |
tree | 4661c233739de7eddb777c2cfd86de95a6963a85 | |
parent | 6a9394b5d1c4401679c87ff130fb8cf028439d08 [diff] |
Simplify the interface of `ArtifactExpander`. * Rename `expand()` to `expandTreeArtifact()` since it is only for tree artifacts. * Return an `ImmutableSortedSet<TreeFileArtifact>` instead of adding children to an output parameter. This should reduce CPU and garbage a bit, as callers can use the `ImmutableSortedSet` instance stored in the `TreeArtifactValue` instead of constructing a temporary collection. * Rename `getFileset()` to `expandFileset()` for naming consistency. * Accept `Artifact` instead of `SpecialArtifact` in `getArchivedTreeArtifact()` for consistency and to reduce casting in callers. PiperOrigin-RevId: 625365709 Change-Id: Ibbda585b8178b173be51c1b79eab5b5e616a38ff
{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