Prototype for remote execution using gRPC and Netty transport

This change implements a remote worker that executes work (build or test).
Bazel will be a client of the remote worker. The communication uses gRPC
and Netty as transport.

A single remote worker has little advantage over running locally. Additional
infrastructure is needed to run workers on multiple machines and distributing
the work among them.

This change provides the basic building blocks for a distributed build farm.

(Mainly reformatting changes compared to https://bazel-review.googlesource.com/3110, some BUILD file changes.)

--
Change-Id: If7d285444ef42a6823b59443af17b61b04b9ce6a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3110/
MOS_MIGRATED_REVID=122376861

1 files changed, 19 insertions, 0 deletions

diff --git a/WORKSPACE b/WORKSPACE
index 8a8dc2cb2b..786c6d8b1c 100644
--- a/WORKSPACE
+++ b/WORKSPACE
@@ -19,6 +19,25 @@ bind(
     actual = "//:dummy",
 )
 
+# Protobuf code generation for GRPC requires three external labels:
+# //external:grpc-java_plugin
+# //external:grpc-jar
+# //external:guava
+bind(
+    name = "grpc-java-plugin",
+    actual = "//third_party/grpc:grpc-java-plugin",
+)
+
+bind(
+    name = "grpc-jar",
+    actual = "//third_party/grpc:grpc-jar",
+)
+
+bind(
+    name = "guava",
+    actual = "//third_party:guava",
+)
+
 # For tools/cpp/test/...
 load("//tools/cpp/test:docker_repository.bzl", "docker_repository")
 docker_repository()