| commit | 5e8d8641b96aab91b46495d8a7ad70e85321e87b | [log] [tgz] |
|---|---|---|
| author | Michajlo Matijkiw <michajlo@google.com> | Thu Sep 10 16:03:55 2015 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Sep 11 09:45:22 2015 +0000 |
| tree | 9690138e77d0c95ee84a35d6a17720e24b044f94 | |
| parent | 942f58d2b8731923adda4e13ca4e5757160d8a4e [diff] |
Stop serializing/deserializing Locations as part of Packages They're not cheap to serialize or reconstitute and we don't really need them. This does leave some odd ends around, in particular i decided to keep deserialization context around as i can picture use for it soon. Also return non-null values from all of EmptyLocation's method since while the javadocs declare that LineAndColumn and Path can be null, there does exist code which does not take this into account, this is for another change. -- MOS_MIGRATED_REVID=102758810
{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.