diff options
author | Jakob Buchgraber <buchgr@google.com> | 2017-09-11 15:19:28 +0200 |
---|---|---|
committer | Philipp Wollermann <philwo@google.com> | 2017-09-12 14:03:45 +0200 |
commit | b1d34be6d1aac24a91733d0b2d1a3202b1a564d4 (patch) | |
tree | 8d261a1afc42b9180d601f4ae12da82881dfaed1 /site/docs/build-event-protocol.md | |
parent | dfb1cb21852f6790ee928873b051d74f00c6e7cc (diff) |
docs: mention remote caching in BES documentation
cc: @endobson
Closes #3698.
Change-Id: I12648f4fa284dfee9d56f605dec0d984f8bba3aa
PiperOrigin-RevId: 168222979
Diffstat (limited to 'site/docs/build-event-protocol.md')
-rw-r--r-- | site/docs/build-event-protocol.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/site/docs/build-event-protocol.md b/site/docs/build-event-protocol.md index 88d81fab2e..f3ff5ccbad 100644 --- a/site/docs/build-event-protocol.md +++ b/site/docs/build-event-protocol.md @@ -218,6 +218,22 @@ authentication and TLS infrastructure. For a description of each of these flags, see the [Command-Line Reference](command-line-reference.html). +### Build Event Service and Remote Caching + +The BEP typically contains many references to log files (test.log, test.xml, +etc. ) stored on the machine where Bazel is running. A remote BES server +typically can't access these files as they are on different machines. A way +to work around this issue is to use Bazel with [remote caching]. Bazel will +upload all output files to the remote cache (including files referenced in +the BEP) and the BES server can then fetch the referenced files from the +cache. + +See [GitHub issue 3689] for more details. + +[remote caching](https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/remote/README.md) + +[GitHub issue 3689](https://github.com/bazelbuild/bazel/issues/3689) + [Build Event Protocol]: https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/build_event_stream.proto |