| commit | 34a6df186b245a03d3f3440d1b90823ae047e6f5 | [log] [tgz] |
|---|---|---|
| author | Benjamin Staffin <benley@gmail.com> | Thu Dec 03 11:20:10 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Thu Dec 03 18:37:48 2015 +0000 |
| tree | f087ad94934c079942f629e21f2d023436779330 | |
| parent | c4975fabe94417d8aa793ae2728c29750d42dde2 [diff] |
Drop intermediate zip archive from py_binary output If you feed a py_binary into a pkg_tar to a pkg_deb, you won't want to have the deploy_zip intermediate artifact included in the resulting package. I'm think this change keeps it as an expected byproduct of the build, but drops it from the list of files produced by the y_binary rule. Also trimmed a superfluous chmod from the final concat action. -- Change-Id: Ib2bc05c2e43c7329bd9d92ea034f0c613f7fcbc6 Reviewed-on: https://bazel-review.googlesource.com/#/c/2280 MOS_MIGRATED_REVID=109290774
{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.