The old logic was very fragile. It relied either on legacy/insecure SA
key, or a *specific* account being used with WI.
We switched which account we use for WI, causing it to disable WI.
I don't think we need this subtlety. We already allow opting out of RBE
by the `BAZEL_BUILD_RBE_INSTANCE` variable -- which we already set when
we want to opt out -- so this should be fine. Additionally, the places
we don't want RBE (our private infra) do not have access to RBE, so if
they somehow tried to use it they would fail.
This simplifies the logic, and should re-enable RBE again
* Re-enable RBE (execution for Ubuntu, cache for CentOS).
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: sync .bazelrc and .bazelversion from upstream.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: Kick CI.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: disable RBE execution until we have LARGE_MACHINES.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: allow to override BAZEL_BUILD_RBE_JOBS.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: disable RBE execution in CentOS postsubmit.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: Kick CI.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: Kick CI.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* Re-enable RBE.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: use only RBE cache.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: Kick CI.
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* Add Prow presubmit verifying that the release scripts work.
This was removed in #2475, while retiring CircleCI jobs,
and it backfired 3 commits later...
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
* review: git add prow/proxy-presubmit-release.sh...
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
Kevin Burek