From fcf00de8643c692270e3da4f6de43dc1277d61ad Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Thu, 11 Feb 2021 12:22:21 -0800 Subject: [PATCH] ci: remove BES usages from CI (#40809) Removes BES configuration from CI bazel configuration as it is increasingly seeing timeouts causing failures, but the uploaded results go largely unlooked at. PR Close #40809 --- .circleci/bazel.linux.rc | 7 ------- 1 file changed, 7 deletions(-) diff --git a/.circleci/bazel.linux.rc b/.circleci/bazel.linux.rc index 9bbc339b20..4f6ebc4e43 100644 --- a/.circleci/bazel.linux.rc +++ b/.circleci/bazel.linux.rc @@ -20,11 +20,4 @@ build --local_ram_resources=32768 # All build executed remotely should be done using our RBE configuration. build:remote --google_default_credentials -# Upload to GCP's Build Status viewer to allow for us to have better viewing of execution/build -# logs. This is only done on CI as the BES (GCP's Build Status viewer) API requires credentials -# from service accounts, rather than end user accounts. -build:remote --bes_backend=buildeventservice.googleapis.com -build:remote --bes_timeout=30s -build:remote --bes_results_url="https://source.cloud.google.com/results/invocations/" - build --config=remote