| commit | f4b07dbdb4bf5d4ae2b743d50f8e43ff49770987 | [log] [tgz] |
|---|---|---|
| author | Erik Kuefler <ekuefler@gmail.com> | Wed Aug 12 15:02:06 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Wed Aug 12 15:23:58 2015 +0000 |
| tree | 705757261d37095ecdf88217d33da6c37d4cf222 | |
| parent | a55377241e2ec9f5280744c61302a7eda07d282c [diff] |
Add Skylark rules for groovy_library and groovy_binary. This is a slightly cleaned-up version of the rules from https://github.com/ekuefler/bazel-groovy, which my team has been using for a few months. I'll add the test rules from there separately. -- Change-Id: I07b5270bfdada5244ed82dee617b4997855747d8 Reviewed-on: https://bazel-review.googlesource.com/#/c/1590/ MOS_MIGRATED_REVID=100476149
{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.