| commit | 19ecfc46d1c6d84006a71212a1885e5902ae422f | [log] [tgz] |
|---|---|---|
| author | Googler <shahan@google.com> | Tue Jan 21 16:36:53 2025 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 21 16:38:30 2025 -0800 |
| tree | 5ba34473cc6a10c2ec41b234d022ccedd0ce5d8a | |
| parent | dd37d6e470d4c2e5e44caa941fcea883a4a7e3d7 [diff] |
Writes file dependency data when uploading analysis objects. The file dependency data is used to check if a cached analysis object is fresh. In this initial phase, we only write the file dependency data without having clients consume it. Clients skip the file dependency data reference present in the cached value. Now that the logic is a bit more complex, splits out the SelectedEntrySerializer to serialize specific selected values from the FrontierSerializer, in addition to the file dependency data. This change adds a couple of test helpers. * LongVersionGetterTestInjection - to inject LongVersionGetter in tests * FakeInvalidationDataHelper - to add fake invalidation data to test generated cache values. PiperOrigin-RevId: 718118838 Change-Id: I5de30fb7e4a24e704d5c32e0014a39e2230861f5
{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
