| commit | f21d35ead25167ca7191229c7a365ccdf1a2550e | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Oct 06 13:17:43 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Oct 07 08:04:54 2016 +0000 |
| tree | 49b9cc08a87fe8966b524ec95f7c701e1fe87aa5 | |
| parent | d3a0d4f4fa6fd4254eb83eceba2069c8a42cd869 [diff] |
Support srcjar files in filtered gen jar. If a java_library has any srcjar files in its sources attribute, the output of these would be discarded. To make it more robust, invert the jar filter to keep everything *except* source artifact java files. Previously, we would build a manifest containing all the generated java files and use that to filter. This should also be ever so slightly faster since we can skip an action. -- MOS_MIGRATED_REVID=135351129
{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.