| commit | dfe0aeef53bd24f46539cb3c6d1ec7282fbb812d | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Mon Oct 07 09:58:24 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 07 09:59:53 2024 -0700 |
| tree | cc06898c7b5cfddedaeb9b44b92909a78bb89d45 | |
| parent | ae0274497028964751310f4fd15117953bf30806 [diff] |
Use a visitor pattern to consume fileset symlinks. Instead of constructing a `FilesetManifest`, callers use a `Visitor` that is invoked for every symlink in the fileset. This allows for an optimization: when the fileset has no relative symlinks (or we are ignoring relative symlinks), we can do a single-pass visitation without building up maps. Additionally, callers are responsible for concatenating the fileset-relative and execroot-relative paths to their roots. This reduces garbage from concatenating paths, since some callers don't need them. PiperOrigin-RevId: 683222046 Change-Id: I80f04306e7a617d3c3e630c56d96b2c968eb1d42
{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
