| commit | aaff855491f0a6679308c5a6eac43b3a93135bfc | [log] [tgz] |
|---|---|---|
| author | Dino Wernli <dinowernli@gmail.com> | Mon Feb 01 15:37:48 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Feb 02 14:56:57 2016 +0000 |
| tree | acaab0c2bde6618d50f131907329b4a0fca44026 | |
| parent | d68626aea63c1b1937128016bc3a210f896e316c [diff] |
Add a scala_test rule to Bazel This implements a scala_test rule analogous to the java_test rule. It uses the standard scalatest library, and adds the corresponding jar(s) to the WORKSPACE file. The rule is tested by adding a proof-of-concept test target to the scala examples. Link to discussion thread: https://groups.google.com/d/msg/bazel-dev/5Kbbwr11XOA/znTY-H1DBgAJ Fixes #503. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/657 MOS_MIGRATED_REVID=113526680
{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.