From d7cdb03ef792feae5bbe1ae34594de69122cc941 Mon Sep 17 00:00:00 2001 From: Jim MacArthur Date: Fri, 9 Nov 2018 17:06:33 +0000 Subject: Documentation: Update to show new config options --- doc/source/format_project.rst | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/doc/source/format_project.rst b/doc/source/format_project.rst index 8701facb0..e64f19988 100644 --- a/doc/source/format_project.rst +++ b/doc/source/format_project.rst @@ -231,10 +231,24 @@ using the `remote-execution` option: remote-execution: # A url defining a remote execution server - url: http://buildserver.example.com:50051 + execution-service: + url: http://buildserver.example.com:50051 + storage-service: + - url: https://foo.com:11002/ + server-cert: server.crt + client-cert: client.crt + client-key: client.key + +The execution-service part of remote execution does not support encrypted +connections yet, so the protocol must always be http. + +storage-service specifies a remote CAS store and the parameters are the +same as those used to specify an :ref:`artifact server `. -The url should contain a hostname and port separated by ':'. Only plain HTTP is -currently suported (no HTTPS). +The storage service may be the same endpoint used for artifact +caching. Remote execution cannot work without push access to the +storage endpoint, so you must specify a client certificate and key, +and a server certificate. The Remote Execution API can be found via https://github.com/bazelbuild/remote-apis. -- cgit v1.2.1