| commit | 6326f98ed84c2e0677b552cd4af808d482e8749c | [log] [tgz] |
|---|---|---|
| author | Nicolas Lopez <ngiraldo@google.com> | Tue Apr 04 16:22:30 2017 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Apr 04 18:41:42 2017 +0200 |
| tree | 87011dbd8ba8a240f4b78693a6c85b772bbf26a9 | |
| parent | b609b516aea7b297561d5ccbf3b0c61239b63f0f [diff] |
adding more env vars to invalidation list It seems several env vars that are used by cc_configure are not in the invalidation list and not included in the bootstrap compile. Adding them. Change-Id: I67f73ae09abbe9033bcbbcb4026dab04d225b699 PiperOrigin-RevId: 152139948
{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.