Skip to content
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

[WIP] Bazel Build Event Stream support #811

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Commits on Nov 1, 2024

  1. BuckEvent: provide a Buck Event Publisher proto

    Provide a BuckEvent Publisher service which emits BuckEvents to an
    external server implementation.
    
    Closes facebook#226
    sluongng authored and aherrmann committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    8203a31 View commit details
    Browse the repository at this point in the history

Commits on Nov 15, 2024

  1. Configuration menu
    Copy the full SHA
    cee321f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    12dc03d View commit details
    Browse the repository at this point in the history
  3. Implement RemoteEventSink to publish to Bazel BES

    Repurposes the RemoteEventSink used to connect to Scribe within Meta internal Buck2 and connects
    it to a Bazel Build Event Service over gRPC instead. Adds a translation layer between Buck2
    build events and Bazel build events.
    aherrmann committed Nov 15, 2024
    Configuration menu
    Copy the full SHA
    81b1763 View commit details
    Browse the repository at this point in the history

Commits on Nov 22, 2024

  1. Publish target, action, and failure information

    BuildBuddy uses pattern expand messages to collect the set of targets to report on.
    Buck2 does not have a direct correspondance to the target completed message, for now we collect all
    targets for which actions are completed and then emit a series of target completed events before we
    close the stream.
    Stdout and stderr are only included inline in Buck2 and not as CAS items, so we forward them as
    inline data.
    Failure details are used by BuildBuddy to display build errors in the UI, so we emit these.
    aherrmann committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    5b8a6ef View commit details
    Browse the repository at this point in the history