Remote Execution Overview
Stay organized with collections
Save and categorize content based on your preferences.
This page covers the benefits, requirements, and options for running Bazel
with remote execution.
By default, Bazel executes builds and tests on your local machine. Remote
execution of a Bazel build allows you to distribute build and test actions
across multiple machines, such as a datacenter.
Remote execution provides the following benefits:
Faster build and test execution through scaling of nodes available
for parallel actions
A consistent execution environment for a development team
Reuse of build outputs across a development team
Bazel uses an open-source
gRPC protocol
to allow for remote execution and remote caching.
For a list of commercially supported remote execution services as well as
self-service tools, see
Remote Execution Services
Requirements
Remote execution of Bazel builds imposes a set of mandatory configuration
constraints on the build. For more information, see
Adapting Bazel Rules for Remote Execution.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-01-22 UTC."],[],[]]
