| commit | 08663e6cb80b256736a9f201df6e06f908589f32 | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Fri Feb 12 09:59:22 2016 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Fri Feb 12 15:24:09 2016 +0000 |
| tree | 9e400725a23e2d8d41a8c7f531602d7da003f01c | |
| parent | 10b24a7102c4221fbeb9e3cdbe87822e1fa51377 [diff] |
Add an experimental flag to enable the Skyframe-based loading phase runner. Refactor the CommandEnvironment to no longer create a LoadingPhaseRunner eagerly. Unfortunately, that means we can't reuse the TargetPatternEvaluator either. Fortunately, the SkyframeTargetPatternEvaluator is a very lightweight class, which only contains the offset as state, so we just create a new instance whenever we need one. On the plus side, the LoadingPhaseRunner API is now stateless, and the QueryCommand no longer creates a unnecessary LoadingPhaseRunner instance. -- MOS_MIGRATED_REVID=114519731
{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.
An 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.