summaryrefslogtreecommitdiff
path: root/doc/source/arch_remote_execution.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/source/arch_remote_execution.rst')
-rw-r--r--doc/source/arch_remote_execution.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/arch_remote_execution.rst b/doc/source/arch_remote_execution.rst
index efefc84b5..9c8e9d354 100644
--- a/doc/source/arch_remote_execution.rst
+++ b/doc/source/arch_remote_execution.rst
@@ -8,7 +8,7 @@ The previous section :ref:`sandboxing` describes the two forms of local sandbox:
Artifact caches and other storage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-BuildStream can transmit the results of local builds to remote artifact caches and retrieve them later. The same mechanism is used for remote execution. The filesystem staged before building is stored in a local content-addressable store, which may be the same as the local artifact cache. The command to execute is also stored as an object in local CAS. Both the initial source filesystem and command are transmitted to remote storage specific to the remote execution service, and after the build is complete, the filesystem after build is retrieved from remote storage to the local CAS. The remote execution service uses the same communication protocol as artifact caches, and may use the same internal storage, but may not implement the extensions used by BuildStream to store full artifacts.
+BuildStream can transmit the results of local builds to remote artifact caches and retrieve them later. The same mechanism is used for remote execution. The filesystem staged before building is stored in a local content-addressable store, which may be the same as the local artifact cache. The command to execute is also stored as an object in local CAS. Both the initial source filesystem and command are transmitted to remote storage specific to the remote execution service, and after the build is complete, the filesystem after build is retrieved from remote storage to the local CAS. The remote execution service uses the same communication protocol as artifact caches, and may use the same internal storage, but may not implement the Remote Asset API used by BuildStream to store full artifacts.
.. image:: images/arch-remote-execution.svg
:align: center