| commit | 930bf691af499e39c00f473a7281f864c67c111b | [log] [tgz] |
|---|---|---|
| author | Erik Kuefler <ekuefler@gmail.com> | Fri Jan 08 15:59:00 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Jan 11 09:39:07 2016 +0000 |
| tree | 1a86cb9bf0e342f6b022349bbc7239e34bd42e0a | |
| parent | 1518253ea86e0f49aceba06ab744de1c27bab5f9 [diff] |
Implement groovy_junit_test This is very similar to spock_test, except it refers to the test classes as "Tests" instead of "Specs", and it doesn't include the dependency on Spock. This is the last of the Groovy rules I'm planning to contribute, though there are a couple of improvements left to be made to the existing rules. -- Change-Id: Ie5acea7f65fcc96ec8cff9a3f9079583e7f77cb7 Reviewed-on: https://bazel-review.googlesource.com/#/c/2431/ MOS_MIGRATED_REVID=111694856
{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.