bazelbuild/bazel

Add support for no-local execution requirement

Open

#26.654 geöffnet am 29. Juli 2025

Auf GitHub ansehen
 (6 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Java (4.465 Forks)batch import
P3help wantedteam-Local-Exectype: feature request

Repository-Metriken

Stars
 (25.384 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 22T 20h) (77 gemergte PRs in 30 T)

Beschreibung

Description of the feature request:

I saw "no-local" as an execution requirement here:

https://github.com/bazelbuild/bazel/blob/3be81016f463d7a19cef5f00fee89efdd887c1b6/src/main/java/com/google/devtools/build/lib/actions/ExecutionRequirements.java#L243

But I was told that this is only for the internal Blaze, not Bazel. Can we have support for "no-local" in Bazel as well?

Which category does this issue belong to?

No response

What underlying problem are you trying to solve with this feature?

Similar to "no-remote" or "no-sandbox", sometimes I need to ensure an action to be ALWAYS executed with some level of isolation. For me, this means this particular action can use process-wrapper, linux-sandbox, or RBE. This particular action writes to the source tree, so it can't use the local strategy to avoid it to actually write to the source tree.

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

8.3.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

https://github.com/bazelbuild/bazel/blob/3be81016f463d7a19cef5f00fee89efdd887c1b6/src/main/java/com/google/devtools/build/lib/actions/ExecutionRequirements.java#L243

Contributor Guide