| commit | 8b3b918ebd55911a3102f5ea6da60906fa63c866 | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Thu Apr 14 08:29:05 2016 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Thu Apr 14 11:11:15 2016 +0000 |
| tree | 5441d1a77d4f89a3450523979b49f8aa63fe4596 | |
| parent | 386f242788a3d0189e6882466105c57ec1149d20 [diff] |
Add the --grpc_port startup option and start a Java server if it's passed in. Note that the presence of server/grpc_port does not guarantee that the server actually listens to it and we can't guarantee it, either, because it can always be kill -9'd. I haven't decided yet how the transition between AF_UNIX and gRPC will work. For now, I'm happy that we can start up a Java server. The way to get the kernel-chosen port is truly awful, but it is apparently impossible to do so in a different way: https://github.com/grpc/grpc-java/issues/72 -- MOS_MIGRATED_REVID=119828354
{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.