| commit | f8f1be3626edb6244eebe48fa6f36bea6275d72c | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed May 04 15:36:15 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Wed May 04 18:32:11 2016 +0000 |
| tree | e77f22cf0557577df69dd95ab2aa6abce734c39d | |
| parent | 54fc221026b9dafec6aa0e65ce01aa90d3be2747 [diff] |
Rollback of commit c9f2881f2540a7aa7c5f6d76f4bdad5d35d1c3b6. *** Reason for rollback *** Seems to have broken exoblaze builds. https://paste.googleplex.com/5185376662585344 happens when rebuilding after a trivial change (removed a single method). *** Original change description *** Rollforward of "Workaround for duplicate input basename bug in apple's libtool", with regex fix -- MOS_MIGRATED_REVID=121483994
{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.