Delay updating inputs of an action when processing the action cache until it is known that the action is a cache hit.

This adds momentary memory overhead when checking the action cache, but should prevent a host of potential errors.

Note that this cl assumes that an action that discovers its inputs does *not* take the names of its inputs into account when calculating its key, which is already stated as part of the javadoc of Action#getKey.

--
MOS_MIGRATED_REVID=88971626
6 files changed
tree: 11338ff270a4d9a0b319ab10dfbfa97244ac4d4f
  1. base_workspace/
  2. docs/
  3. scripts/
  4. src/
  5. third_party/
  6. tools/
  7. .gitignore
  8. .travis.yml
  9. bootstrap_test.sh
  10. compile.sh
  11. LICENSE.txt
  12. README.md
  13. WORKSPACE
README.md

Bazel

{Fast, Correct} - Choose two

Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:

  • A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.

  • A emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.

  • Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.

Find more background about Bazel in our FAQ

Getting Started