bes: add BES and BEP protocol crates#995
Open
sluongng wants to merge 3 commits into
Open
Conversation
facebook-github-bot
added
the
CLA Signed
Contributor
|
@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. (Because this pull request was imported automatically, there will not be any future comments.) |
Contributor
Author
|
Technically, the BES proto is also part of the googleapis repository, but I think it's worth splitting into a separate crate to avoid build cache churn. cc: @avdv @aherrmann |
sluongng
force-pushed
the
sluongng/bes-proto
branch
from
June 13, 2025 16:25
0326148 to
11f9b21
Compare
sluongng
force-pushed
the
sluongng/bes-proto
branch
from
June 26, 2026 07:46
11f9b21 to
06c9dc4
Compare
sluongng
changed the title
The remote-execution proto crate currently owns common Google API, Bytestream, long-running operation, and status definitions. Move those definitions into a shared crate because BES needs the same types and compiling duplicate packages would create incompatible Rust types. Keep re_grpc_proto re-exporting them so existing users retain their API.
sluongng
force-pushed
the
sluongng/bes-proto
branch
from
July 22, 2026 13:45
06c9dc4 to
87416a3
Compare
sluongng
changed the title
Buck2's OSS build does not provide generated Bazel Build Event Protocol types, which blocks interoperable event conversion. Add a dedicated crate for the canonical BEP definitions because later publishing code needs Bazel-compatible messages without coupling them to remote execution or transport concerns.
The OSS build cannot construct or publish canonical Build Event Service messages because it lacks generated service types. Add a dedicated BES crate wired to shared Google API protos so later event sinks can use standard lifecycle and streaming RPCs without modifying remote-execution types.
sluongng
force-pushed
the
sluongng/bes-proto
branch
from
July 22, 2026 14:44
87416a3 to
b0c5c9e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The OSS build has no generated bindings for Bazel's Build Event Protocol
or the Build Event Service, which blocks interoperable build-event
publishing.
Add separate BEP and BES crates, and move shared Google API, Bytestream,
long-running operation, and status definitions out of
re_grpc_protobecause both remote execution and BES need identical Rust types. The
three commits keep the shared types, BEP schema, and BES service schema
independently reviewable.
The vendored snapshots preserve their upstream Apache license headers.
Provider-specific extensions present in the fork snapshots are omitted,
and generated code is linted using the repository's existing generator
conventions.
This PR adds protocol bindings only. It does not add a BES client, a
Buck-to-BEP converter, invocation UI, or default-on publishing behavior.