commit | 8618b9d67d20a737908113fa89357ac321a9669b | [log] [tgz] |
---|---|---|
author | Michael Staib <mstaib@google.com> | Fri Sep 16 19:36:49 2016 +0000 |
committer | Laszlo Csomor <laszlocsomor@google.com> | Mon Sep 19 07:35:07 2016 +0000 |
tree | c35e40647b56648f25716aa209525257619ea664 | |
parent | 1ca32990938c4b126cbe49895b757403e8fbf07a [diff] |
Add deprecation support to Bazel. Bazel has always had a deprecation attribute, but until now it has been a no-op. After this change, Bazel will warn when a target with the deprecated attribute unset depends on one with the deprecated attribute set. Like all other warnings, this warning will only be displayed when it matches the output filter. It is also bypassed if the two targets are in the same package. RELNOTES: The deprecation attribute of all rules now causes warnings to be printed when other targets depend on a target with that attribute set. -- MOS_MIGRATED_REVID=133415232
{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.