| commit | 4f7c859f6dfb3402a1adfe9346228695caa1b2b2 | [log] [tgz] |
|---|---|---|
| author | Googler <shahan@google.com> | Tue Oct 22 15:29:13 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 22 15:30:15 2024 -0700 |
| tree | 18de2d391af1136c416732e2a7f3490a61683965 | |
| parent | 744de79519ff2db3cda7f1fbe6e207374808cf0f [diff] |
Add NestedFileSystemOperationNodes, canonical wire format and round-tripping. Since NestedFileSystemOperationNodes are identified by a fingerprint of their serialized representation uses a custom, canonical wire format. As per https://protobuf.dev/programming-guides/serialization-not-canonical/, protos are not canonical. Performs some renamings for consistency. * In some places renames Directory to Listing. This emphasizes that it's the listing that matters for invalidation. * For consistency, some places that were DirectoryListing are also renamed as Listing. * GetDependenciesResult is renamed to GetFileDependenciesResult for consistency. PiperOrigin-RevId: 688712493 Change-Id: I0456a3d7ab0a8f4077d057d9ded3f1061fd85d11
{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
