| commit | 6adba3ba33ec834b9671d03ab823225639724f99 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Jun 29 17:25:27 2016 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Thu Jun 30 11:40:58 2016 +0000 |
| tree | 33774707a109766815c5211ff1e38bb6a52621c5 | |
| parent | d8be627b765429ca6c64a7e930deb624de03e651 [diff] |
Rollback of commit 368cc56fb2baa3e21be4acdd2410a4ce8245de93. *** Reason for rollback *** Broke builds that use apple_genrule. *** Original change description *** Move platform environment from xcrun_action to apple_action. This change ensures that scripts that don't need to be wrapped with xcrun_action (like actoolwrapper, ibtoolwrapper, and friends, because they internally invoke xcrunwrapper) also have the Xcode version and platform envvars set. RELNOTES: -- MOS_MIGRATED_REVID=126205606
{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.