Bug: 129998295

Clone this repo:
  1. e0e5a53 Merge branch 'aosp/upstream-master' by Dan Willemsen · 5 years ago build-tools-release main master
  2. 1a875d7 Initial empty repository by Inna Palant · 5 years ago
  3. 6a5a17b Adding C++ gRPC libraries. Also fixing build for latest Bazel. (#64) by Ola Rozenfeld · 5 years ago
  4. cfe8e54 Clarify semantics around do_not_cache and skip_cache_lookup (#55) by Eric Burnett · 5 years ago
  5. 7b53872 Create CODEOWNERS (#53) by Dmitry Lomov · 5 years ago

Remote Execution API

The Remote Execution API is an API that, at its most general, allows clients to request execution of binaries on a remote system. It is intended primarily for use by build systems, such as Bazel, to distribute build and test actions through a worker pool, and also provide a central cache of build results. This allows builds to execute faster, both by reusing results already built by other clients and by allowing many actions to be executed in parallel, in excess of the resource limits of the machine running the build.

There are a number of clients and services using these APIs, they are listed below.


These tools use the Remote Execution API to distribute builds to workers.


These applications implement the Remote Execution API to server build requests from the clients above. These are then distributed to workers; some of these workers implement the Remote Worker API.


The APIs in this repository refer to several general-purpose APIs published by Google in the Google APIs repository. You will need to refer to packages from that repository in order to generate code using this API. If you build the repository using the included BUILD files, Bazel will fetch the protobuf compiler and googleapis automatically.

Using the APIs

The repository contains BUILD files to build the protobuf library with Bazel. If you wish to use them with your own project in Bazel, you will possibly want to declare cc_proto_library, java_proto_library, etc. rules that depend on them.

Other build systems will have to run protoc on the protobuf files, and link in the googleapis and well-known proto types, manually.