| commit | de62b4e9cd0f56473278811774ec191a4e0fafcd | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Fri Feb 26 13:13:39 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Sun Feb 28 17:04:23 2016 +0000 |
| tree | d5f18446ad3935c35340f84f0fcab7d3dceb47c3 | |
| parent | b8101f57681f292a9ec312a9cbbc84ac4ec0668d [diff] |
Pass the source path -> Artifact mapping into FdoSupport from a provider instead of special-casing it. This removes the need to deserialize artifacts in FdoSupport, which in turn removes the need to support artifact deserialization at all, which makes our lives simpler and Thoreauvian programming is good. -- MOS_MIGRATED_REVID=115660698
{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.