| commit | 4215114379eebb91ae502f626366873f47af9e4e | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Tue Apr 18 16:42:25 2017 +0200 |
| committer | Klaus Aehlig <aehlig@google.com> | Wed Apr 19 10:46:33 2017 +0200 |
| tree | 3947121b67c18567220936058a359403ac5d04ee | |
| parent | 3a5d3db6436bbaf5351da9ea9c19a41ae7c95ca9 [diff] |
Revert "Expect the python binary on path to be a symlink " This reverts commit 1cd2096284959ead26687d1d58b695d2abffb8e2. That commit tried to find a more suitable python binary by following symlinks. That, however, is not necessary, as our follow-up infrastructure can call symbolic links and our tests os.path.isfile(path) and os.access(path, os.X_OK) follow symbolic links as well. Fixes #2836. Change-Id: If37589622d141265577eb3872f68342ae1c263dc PiperOrigin-RevId: 153461118
{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.