| commit | 015edb05335fa26a2021827502d368dbc154e9ae | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Thu Jan 26 13:22:31 2017 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Thu Jan 26 14:53:53 2017 +0000 |
| tree | 0307652285e2b02cf86c104fd296dd62db5fcb58 | |
| parent | dd04adf4877963e76ac83018b46e87ad1c3095b3 [diff] |
Rollback of commit 96297ed7a9ab3df0f45e93bae9d71833f4195334. *** Reason for rollback *** Roll-forward with fix *** Original change description *** Automated [] rollback of commit ffc0d2df0213123a4451bed5850827319afcdeee. *** Reason for rollback *** Grr I knew I shouldn't have done 2 changes in one tests are failing now Fixes #2429. *** Original change description *** Release scripts: factor out the push to notes and fix a typo -- PiperOrigin-RevId: 145662713 MOS_MIGRATED_REVID=145662713
{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.