| commit | 0cf3821123c2c697041600179a2a308188c9e313 | [log] [tgz] |
|---|---|---|
| author | Thiago Farina <tfarina@chromium.org> | Mon May 08 04:17:01 2017 -0400 |
| committer | Kristina Chodorow <kchodorow@google.com> | Mon May 08 09:49:16 2017 -0400 |
| tree | b3ae7b93d3a605a725d6ff05ce26b7841b5121f1 | |
| parent | fefced3743b6fb4f66580687f4cfd656d8bf62b4 [diff] |
cpp: do not mention -1 for command_port option -1 is not a valid port number and thus do not mean "no gRPC command server". If you try to pass -1 to command_port you get: $ bazel --command_port=-1 build //... Invalid argument to --command_port: '-1'. Must be a valid port number or 0. Change-Id: I6c17167f6a285b21fcd064cea8bdc7e6770ac984 PiperOrigin-RevId: 155352835
{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.