| commit | 691fbc1a5fd3ab03ab6c21e6c04fa9c528bbf1ba | [log] [tgz] |
|---|---|---|
| author | John Cater <jcater@google.com> | Tue Feb 28 13:15:28 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Feb 28 17:02:08 2017 +0000 |
| tree | 3235bb9c6a3382f40e0bf1a933a22b2967a23c69 | |
| parent | 55e4c51ac76f1da3537f33536c1d2bfea15e5b93 [diff] |
Add constraint_setting and constraint_value rules, to enable defining platform-related constraints and values. Part of ongoing work on #2219. -- Change-Id: Ice370ee26469f4992faf72c0c95a1a3e51a9f9e7 Reviewed-on: https://cr.bazel.build/9091 PiperOrigin-RevId: 148758190 MOS_MIGRATED_REVID=148758190
{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.