Remove ArtifactFileMetadata and replace it with FileArtifactValue. A harmful side effect is the loss of the "digest must be present" assertion on RegularFileArtifactValue. I'm not a fan of this, however, in practice: - There are other kinds of FileArtifactValues and it's not clear whether they are supposed to have digests or not - The important invariant, that ActionExecutionValue supplies a digest in all sane cases, is not upheld at HEAD because ArtifactFileMetadata is not guaranteed to contain one. The game plan is to re-instate that check when ActionExecutionValue is constructed (somehow) after getting rid of the PLACEHOLDER silliness, if possible. In exchange, however, we get a saner treatment of output directories: before this change, we created ArtifactFileMetadata instances for them even though they were not, well, files. RELNOTES: None. PiperOrigin-RevId: 260909718
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.