From 131e2440f2acd842c3cfbca02499a57f44bfd668 Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Fri, 21 Jun 2019 12:38:35 -0700 Subject: [PATCH] build: Set up Build Event Service Configuration for RBE executed bazel (#31197) The Build Event Service (https://docs.bazel.build/versions/master/build-event-protocol.html#the-build-event-service), allows for build events from bazel builds to be transmitted as opaque bytes to be processed. Our usage is to send our build events to a Build Event Service an Angular team owned Google Cloud Project which collects build results and makes each invocation available via a provided URL to view. The information uploaded includes information about the build environment, configuration, build status/events, build options, results and actions. Build Event Protocol Proto: https://github.com/bazelbuild/bazel/blob/0.27.0/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/build_event_stream.proto PR Close #31197 --- .bazelrc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.bazelrc b/.bazelrc index 6a3ab9fb02..4b73feba4a 100644 --- a/.bazelrc +++ b/.bazelrc @@ -137,11 +137,17 @@ build:remote --platforms=//tools:rbe_ubuntu1604-angular # Remote instance. build:remote --remote_instance_name=projects/internal-200822/instances/default_instance +build:remote --project_id=internal-200822 # Do not accept remote cache. # We need to understand the security risks of using prior build artifacts. build:remote --remote_accept_cached=false +# Build Event Service Configuration +build:remote --bes_backend=buildeventservice.googleapis.com +build:remote --bes_timeout=30s +build:remote --bes_results_url="https://source.cloud.google.com/results/invocations/" + ############################### # NodeJS rules settings # These settings are required for rules_nodejs