commit | ba04b2d2d2466540c39c93539285d7c97216272a | [log] [tgz] |
---|---|---|
author | Brian Silverman <bsilver16384@gmail.com> | Tue Jan 19 16:46:10 2016 +0000 |
committer | Han-Wen Nienhuys <hanwen@google.com> | Wed Jan 20 11:34:14 2016 +0000 |
tree | 6d04ddcb7ad1aa3534ca1429f86e46b31f83a2ca | |
parent | d03f32142ca0e05cc87855337557f8ea33972658 [diff] |
Create a wrapper script which looks for an executable in the workspace This executable in the workspace can be another Bazel binary whose version will change with the code it's next to, or a shell script which downloads a fixed version from some location. RELNOTES: A tools/bazel script in the workspace will be executed as an opportunity to use a fixed version of Bazel (not implemented for the homebrew recipe yet). Fixes #521 -- Change-Id: Id06177d9c2b259cd9d6fd62edb5abe541342dd05 Reviewed-on: https://bazel-review.googlesource.com/2620 MOS_MIGRATED_REVID=112477232
{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.