bazelbuild / bazelbuild/reclient
Add Build Event Service (BES) support
- Dominant language
- Go
- Stars
- 114
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
The [Build Event Protocol](https://bazel.build/remote/bep) (BEP) allows third-party programs to gain insight into a Bazel invocation. It includes information about build and test results, build progress, the build configuration and much more. The [Build Event Service](https://bazel.build/remote/bep#build-event-service) (BES) Protocol is a generic gRPC service for publishing BEP events.
Cloud-based RBE systems intended for use with Bazel builds often use BES reporting to track progress and resource utilization associated with a particular build. Lack of BES support can be a blocker for reclient use with these systems.
Contributor guide
Research direction
No repository files, tests, or entry points are named. Start by reviewing the linked Build Event Protocol and Build Event Service documentation, then map the required integration points in reclient. Done means reclient can publish BEP events to a BES endpoint and the behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100