commit | c35878a258d3c8a5305389aadd17ac0049defa15 | [log] [tgz] |
---|---|---|
author | lberki <lberki@google.com> | Thu Aug 01 02:28:54 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 01 02:29:50 2019 -0700 |
tree | b1d15b114c0f25563cb78633e19aabea98c4c550 | |
parent | e764670427e526c01c4ca5b44b5e23120ed4b73d [diff] |
Remove {OutputStore,ActionExecutionValue}.additionalOutputData. Instead of having another map, when additional data is needed, replace artifactData with it. There was one place where we exploited the difference between the two: for cases where we get a digest from remote execution but one is not available for the file system, FilesystemValueChecker used only one map. I fixed this by adding a method to FileArtifactValue that tells whether given two instances, Blaze should assume that there was no change and replicated the existing behavior as faithfully as possible. RELNOTES: None. PiperOrigin-RevId: 261086332
{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.