| commit | 3bed4af4f27bbd22b5531454095f0eda30bfac9f | [log] [tgz] |
|---|---|---|
| author | Philipp Schrader <philipp@peloton-tech.com> | Wed Jul 20 10:34:27 2016 +0000 |
| committer | John Cater <jcater@google.com> | Wed Jul 20 15:01:33 2016 +0000 |
| tree | 250d302e861ff50390b42b78cdeba82b91496f0d | |
| parent | 279007ddfcdb6857b9c3cd3fcf015ba7f47a4c55 [diff] |
Use exec in py_binary to avoid child processes The current approach for the py_binary wrapper means that deployed instances of py_binary targets create child processes. This can be a problem when you try to kill the py_binary target since signals and such don't necessarily get passed along to the child process. Using the exec functionality here should avoid this particular problem. The overall behaviour should remain the same. -- Change-Id: I20ef081e1da5b28a8aff8514d713b1c387ae7f7e Reviewed-on: https://bazel-review.git.corp.google.com/#/c/4070/ MOS_MIGRATED_REVID=127929454
{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.