commit | 6b3c21cb4886314f932e58e5f08fab141b046eb1 | [log] [tgz] |
---|---|---|
author | Googler <shahan@google.com> | Mon Oct 21 17:32:53 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 21 17:34:10 2024 -0700 |
tree | 5ca33e406a7bdea89c0d399304082bcb818745b1 | |
parent | bd5204664bbeb57a134ba14b42f1007a8f2b15ba [diff] |
Move FileValue.Key and DirectoryListingValue.Key into the same JAR file. Also moves FileValue.FILE to SkyFunctions.FILE. Gives FileKey and DirectoryListingKey a common, sealed based type, FileSystemOperationNode, which induces a cyclic dependency between these types, requiring them to be in the same JAR file. The next change will introduce a NestedSet-like type for these using a composite pattern. Giving them a common sealed base type preserves type-safety while avoiding unnecessary wrappers for unary nodes. PiperOrigin-RevId: 688331584 Change-Id: Ic3971ef49ab4d74663cab2cfe35e523bd88aebff
{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