| commit | c6c516dda8083caa42a60db7b82fcf52647a8cb3 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Tue Apr 12 13:37:58 2016 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Wed Apr 13 08:08:35 2016 +0000 |
| tree | 2650e9ba37f1a7b462d03cb902d3217f62233cc8 | |
| parent | 5215d1e804a830e256a7dc23c44f737a332495f4 [diff] |
Make the genproto rules of Bazel usable from other repositories. This is mainly so that Dash can be fixed. It's not the optimal solution because then Dash will pull in the whole Bazel repository for a tiny little part of it, though. The optimal solution would be to make Bazel use WORKSPACE dependencies and then factor it out to a separate repository, but this will be good enough to unbreak Dash for the time being. Progress toward fixing https://github.com/bazelbuild/dash/issues/12 . -- MOS_MIGRATED_REVID=119633183
{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.