Description of the problem / feature request:
Currently, if you set a manual --spawn_strategy that includes remote, but remote_executor isn't set, you get an error about an unknown spawn strategy (because the RemoteModule isn't loaded). This makes it very difficult to customize the spawn strategy that should be used (e.g. disabling sandboxing on macOS, but conditionally enabling remote execution).
Instead of preventing remote, it should simply ignore it if remote_executor is not set. This would allow customizing the default --spawn_strategy (which conditionally adds remote).
Feature requests: what underlying problem are you trying to solve with this feature?
The ability to easily customize --spawn_strategy while conditionally using remote execution.
What operating system are you running Bazel on?
macOS
What's the output of bazel info release?
release 4.0.0
Description of the problem / feature request:
Currently, if you set a manual
--spawn_strategythat includesremote, butremote_executorisn't set, you get an error about an unknown spawn strategy (because theRemoteModuleisn't loaded). This makes it very difficult to customize the spawn strategy that should be used (e.g. disabling sandboxing on macOS, but conditionally enabling remote execution).Instead of preventing
remote, it should simply ignore it ifremote_executoris not set. This would allow customizing the default--spawn_strategy(which conditionally addsremote).Feature requests: what underlying problem are you trying to solve with this feature?
The ability to easily customize
--spawn_strategywhile conditionally using remote execution.What operating system are you running Bazel on?
macOS
What's the output of
bazel info release?release 4.0.0