| commit | 2c2d19007818204e552f47ffe8721322a7ff8558 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Dec 07 16:53:32 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Wed Dec 07 22:20:17 2016 +0000 |
| tree | a771fab4309e184b4e55fa3a4ffadb0cdc1201cf | |
| parent | dc388246ff56d4cdd95fbeebba7f78ff3097e0c4 [diff] |
Pass isExternal field to blaze ide info proto Roll forward after fixing tests. Changes from rolled-back CL: Native aspect now determines 'isExternal' identically to skylark aspect. RepositoryName.isMain was unreliable (at least in testing environment), because unknown repos (occurring due to some race condition) are flagged as being in the 'default' repo, distinct from the 'main' repo. We now bypass RepositoryName entirely, and use the same label string heuristic as used in the Skylark aspect. -- PiperOrigin-RevId: 141314075 MOS_MIGRATED_REVID=141314075
{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.