| commit | 629a7c4d97efbb4b2001650f30f9168968ffa9e7 | [log] [tgz] |
|---|---|---|
| author | Janak Ramakrishnan <janakr@google.com> | Thu Oct 15 20:16:04 2015 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Fri Oct 16 07:40:19 2015 +0000 |
| tree | 1a5c84cf68cb1060f52f3e3a13729e51f59dba32 | |
| parent | dda3f8c8e2d088ba5d8640dfa20651ce71d0e535 [diff] |
Stop filtering when returning root causes -- the filter is always true, since root causes are associated with top-level targets and labels, and the filter is for all top-level targets and labels. I noticed this when a huge --noanalyze build spent most of its time in filtering here. The passed-in "collection" was a list, which meant that we could have sped it up by using a set, but why not just get rid of it all. -- MOS_MIGRATED_REVID=105536485
{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.