-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: Set up Build Event Service Configuration for RBE executed bazel #31197
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add some more info in the commit message on what is Build Event Service (maybe add a link to https://docs.bazel.build/versions/master/build-event-protocol.html#the-build-event-service or some other relevant resource) and what this PR does (e.g. where does it send the data, when does it send it, etc.).
It might be obvious to people using blaze/bazel for years, but it is not so obvious for the uninitiated 😛
OOC, why is this |
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
7ad7cbc
to
3486546
Compare
I marked it as master only since it was only modifying how remote builds are done (so currently only CI in earnest), but I suppose this could target |
#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
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Uploads bazel events to the build event service when run with
config=remote