From 6c509c2ad08b5e7fc29f15154b2154bcac646b97 Mon Sep 17 00:00:00 2001
From: David Ostrovsky <david@ostrovsky.org>
Date: Wed, 3 Mar 2021 11:30:50 +0100
Subject: [PATCH] Remove obsolete Bazel spawn strategies

After the latest Bazel upgrade, the --spawn_strategy=standalone
doesn't show the output of the subprocess created, making the
troubleshoot of the failures impossible.

Since release 0.27 Bazel auto detects the execution strategy, if no
strategy flag is provided. If none of the strategy flags was used,
Bazel will generate a default list of strategies (in this order):

   remote,worker,sandboxed,local

and, for every action it wants to execute, will pick up the first
strategy that can execute it.

See this blog entry for more details: [1].

[1] https://blog.bazel.build/2019/06/19/list-strategy.html

Change-Id: I4be8375cee88f3565bae5c53cd1a3484ce398aba
---
 roles/bazelisk-build/tasks/main.yaml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/roles/bazelisk-build/tasks/main.yaml b/roles/bazelisk-build/tasks/main.yaml
index e75e0f97a4..1d70fdcd67 100644
--- a/roles/bazelisk-build/tasks/main.yaml
+++ b/roles/bazelisk-build/tasks/main.yaml
@@ -5,8 +5,6 @@
     {{ bazelisk_executable }} version
     {{ bazelisk_executable }} \
       build \
-      --spawn_strategy=standalone \
-      --genrule_strategy=standalone \
       {{ bazelisk_targets|join(' ') }}
   args:
     executable: /bin/bash