| commit | 86b9fef6e5c753013a4fdee75093ea8d95116ae4 | [log] [tgz] |
|---|---|---|
| author | David Santiago <david.santiago@gmail.com> | Wed Nov 18 14:49:15 2015 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Wed Nov 18 15:32:28 2015 +0000 |
| tree | 38e6713d8d1b8b426938f3639072a5999b0369a1 | |
| parent | 9e1a62ae87feafc9d623a1b036f6ec0348663b76 [diff] |
Update go_binary and go_test rules to copy files in the "data" attribute to runfiles. Add shell-based unit test for runfile support by these rules. -- Change-Id: Ia97278059d104b9728d53aa75c0987fc3c47b640 Reviewed-on: https://bazel-review.git.corp.google.com/#/c/2265/ MOS_MIGRATED_REVID=108139011
{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.