| commit | 9d4193b2cede75de398e737fa620f8d09a8f57fb | [log] [tgz] |
|---|---|---|
| author | Googler <lberki@google.com> | Fri Oct 25 08:06:01 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 25 08:07:18 2024 -0700 |
| tree | eaafeaf8e7742f9e543441d3aed16738166ba7c2 | |
| parent | 5357798b160f4054ade31d109cae4021ff552e26 [diff] |
Track metadata for omitted artifacts also. This was already the case in some scenarios and since we always have the metadata available, it doesn't make sense to keep hold it back. It's useful, for example, for populating the local action cache for actions with omitted outputs. I briefly considered adding an isOmitted() bit to FileArtifactValue but decided against it because it would mean that "omitted-ness" is propagated further than ActionOutputMetadataStore, and why do that if it's not necessary? This means that OMITTED_FILE_MARKER and OMITTED_TREE_MARKER are mostly obsolete. They will be deleted in a followup. change RELNOTES: None. PiperOrigin-RevId: 689791065 Change-Id: I2269bb40495da0e9c54c9155a18cacbd34970eca
{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
