| commit | b8d0902db6e27c671cd2aadfbb03f13e2351c2bb | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Tue Sep 20 13:39:08 2016 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Wed Sep 21 07:04:27 2016 +0000 |
| tree | 18bab103167c75a6e16cf5392b97ee523d928fe3 | |
| parent | 4795564177d5fe62a10bf69acbd6a4f925a0022e [diff] |
Add an info item to show the currently inherited client environment Add 'bazel info client-env' which outputs entries for the configuration file that would freeze the current client environment. The main intended use case is to use 'bazel info client-env >> .bazelrc' to keep the project reproducible once a suitable value for the environment variables that used to be taken from the client environment has been found. -- Change-Id: Ib4d14dd824d223f335a4d4de04ee21c4a3ec4d83 Reviewed-on: https://bazel-review.googlesource.com/#/c/6112 MOS_MIGRATED_REVID=133699234
{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.