| commit | 53abece6ff52869587d907a1884243e64a82592c | [log] [tgz] |
|---|---|---|
| author | Ulf Adams <ulfjack@google.com> | Wed Feb 03 08:30:07 2016 +0000 |
| committer | David Chen <dzc@google.com> | Wed Feb 03 22:06:07 2016 +0000 |
| tree | 130d7185a7b52d74801c4acb661c1762212b9ba8 | |
| parent | 24f04de25d6d899b35ff0541cddef432bc1aeb12 [diff] |
Correctly flag loading errors in the interleaved case. In the interleaved case, loading errors can now also be discovered during the analysis phase. Add a boolean flag to the SkyframeAnalysisResult to indicate that such an error happened, and pass it through in BuildView. Also refactor BuildView to simplify the code a bit - simply pass the SkyframeAnalysisResult to the createResult method. There is already an integration test for this - I'm adding a faster unit test in BuildViewTest, as this is part of the BuildView contract. -- MOS_MIGRATED_REVID=113716870
{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.