package build_event_stream

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Aborted

build_event_stream.proto:237

Payload of an event indicating that an expected event will not come, as the build is aborted prematurely for some reason.

Used in: BuildEvent

enum Aborted.AbortReason

build_event_stream.proto:238

Used in: Aborted

message ActionExecuted

build_event_stream.proto:418

Payload of the event indicating the completion of an action. The main purpose of posting those events is to provide details on the root cause for a target failing; however, consumers of the build-event protocol must not assume that only failed actions are posted.

Used in: BuildEvent

message BuildEvent

build_event_stream.proto:673

Message describing a build event. Events will have an identifier that is unique within a given build invocation; they also announce follow-up events as children. More details, which are specific to the kind of event that is observed, is provided in the payload. More options for the payload might be added in the future.

message BuildEventId

build_event_stream.proto:33

Identifier for a build event. It is deliberately structured to also provide information about which build target etc the event is related to. Events are chained via the event id as follows: each event has an id and a set of ids of children events such that apart from the initial event each event has an id that is mentioned as child id in an earlier event and a build invocation is complete if and only if all direct and indirect children of the initial event have been posted.

Used in: BuildEvent

message BuildEventId.ActionCompletedId

build_event_stream.proto:137

Identifier of an event reporting that an action was completed (not all actions are reported, only the ones that can be considered important; this includes all failed actions).

Used in: BuildEventId

message BuildEventId.BuildFinishedId

build_event_stream.proto:183

Identifier of the BuildFinished event, indicating the end of a build.

Used in: BuildEventId

(message has no fields)

message BuildEventId.BuildMetricsId

build_event_stream.proto:193

Identifier of an event providing build metrics after completion of the build.

Used in: BuildEventId

(message has no fields)

message BuildEventId.BuildStartedId

build_event_stream.proto:52

Identifier of an event indicating the beginning of a build; this will normally be the first event.

Used in: BuildEventId

(message has no fields)

message BuildEventId.BuildToolLogsId

build_event_stream.proto:188

Identifier of an event providing additional logs/statistics after completion of the build.

Used in: BuildEventId

(message has no fields)

message BuildEventId.ConfigurationId

build_event_stream.proto:114

Identifier of an event introducing a configuration.

Used in: ActionExecuted, BuildEventId, ActionCompletedId, ConfiguredLabelId, TargetCompletedId, TestResultId, TestSummaryId

message BuildEventId.ConfiguredLabelId

build_event_stream.proto:158

Identifier of an event reporting an event associated with a configured label, usually a visibility error. In any case, an event with such an id will always report some form of error (i.e., the payload will be an Aborted event); there are no regular events using this identifier.

Used in: BuildEventId

message BuildEventId.FetchId

build_event_stream.proto:80

Identifier of an event reporting that an external resource was fetched from.

Used in: BuildEventId

message BuildEventId.NamedSetOfFilesId

build_event_stream.proto:107

Identifier of an event introducing a named set of files (usually artifacts) to be referred to in later messages.

Used in: BuildEventId, NamedSetOfFiles, OutputGroup

message BuildEventId.OptionsParsedId

build_event_stream.proto:75

Identifier on an event reporting on the options included in the command line, both explicitly and implicitly.

Used in: BuildEventId

(message has no fields)

message BuildEventId.PatternExpandedId

build_event_stream.proto:91

Identifier of an event indicating that a target pattern has been expanded further. Messages of this shape are also used to describe parts of a pattern that have been skipped for some reason, if the actual expansion was still carried out (e.g., if keep_going is set). In this case, the pattern_skipped choice in the id field is to be made.

Used in: BuildEventId

message BuildEventId.ProgressId

build_event_stream.proto:43

Identifier of an event reporting progress. Those events are also used to chain in events that come early.

Used in: BuildEventId

message BuildEventId.StructuredCommandLineId

build_event_stream.proto:61

Identifier on an event describing the commandline received by Bazel.

Used in: BuildEventId

message BuildEventId.TargetCompletedId

build_event_stream.proto:123

Identifier of an event indicating that a target was built completely; this does not include running the test if the target is a test target.

Used in: BuildEventId

message BuildEventId.TargetConfiguredId

build_event_stream.proto:97

Identifier of an event indicating that a target has been expanded by identifying for which configurations it should be build.

Used in: BuildEventId

message BuildEventId.TestResultId

build_event_stream.proto:168

Identifier of an event reporting on an individual test run. The label identifies the test that is reported about, the remaining fields are in such a way as to uniquely identify the action within a build. In fact, attempts for the same test, run, shard triple are counted sequentially, starting with 1.

Used in: BuildEventId

message BuildEventId.TestSummaryId

build_event_stream.proto:177

Identifier of an event reporting the summary of a test.

Used in: BuildEventId

message BuildEventId.UnconfiguredLabelId

build_event_stream.proto:150

Identifier of an event reporting an event associated with an unconfigured label. Usually, this indicates a failure due to a missing input file. In any case, it will report some form of error (i.e., the payload will be an Aborted event); there are no regular events using this identifier. The purpose of those events is to serve as the root cause of a failed target.

Used in: BuildEventId

message BuildEventId.UnknownBuildEventId

build_event_stream.proto:37

Generic identifier for a build event. This is the default type of BuildEventId, but should not be used outside testing; nevertheless, tools should handle build events with this kind of id gracefully.

Used in: BuildEventId

message BuildEventId.UnstructuredCommandLineId

build_event_stream.proto:57

Identifier on an event indicating the original commandline received by the bazel server.

Used in: BuildEventId

(message has no fields)

message BuildEventId.WorkspaceStatusId

build_event_stream.proto:70

Identifier of an event indicating the workspace status.

Used in: BuildEventId

(message has no fields)

message BuildFinished

build_event_stream.proto:595

Event indicating the end of a build.

Used in: BuildEvent

message BuildFinished.ExitCode

build_event_stream.proto:602

Exit code of a build. The possible values correspond to the predefined codes in bazel's lib.ExitCode class, as well as any custom exit code a module might define. The predefined exit codes are subject to change (but rarely do) and are not part of the public API. A build was successful iff ExitCode.code equals 0.

Used in: BuildFinished

message BuildMetrics

build_event_stream.proto:623

Used in: BuildEvent

message BuildMetrics.ActionSummary

build_event_stream.proto:624

Used in: BuildMetrics

message BuildMetrics.MemoryMetrics

build_event_stream.proto:637

Used in: BuildMetrics

message BuildMetrics.PackageMetrics

build_event_stream.proto:656

Used in: BuildMetrics

message BuildMetrics.TargetMetrics

build_event_stream.proto:645

Used in: BuildMetrics

message BuildStarted

build_event_stream.proto:282

Payload of an event indicating the beginning of a new build. Usually, events of those type start a new build-event stream. The target pattern requested to be build is contained in one of the announced child events; it is an invariant that precisely one of the announced child events has a non-empty target pattern.

Used in: BuildEvent

message BuildToolLogs

build_event_stream.proto:664

Event providing additional statistics/logs after completion of the build.

Used in: BuildEvent

message Configuration

build_event_stream.proto:349

Payload of an event reporting details of a given configuration.

Used in: BuildEvent

message Fetch

build_event_stream.proto:332

Payload of an event indicating that an external resource was fetched. This event will only occur in streams where an actual fetch happened, not in ones where a cached copy of the entity to be fetched was used.

Used in: BuildEvent

message File

build_event_stream.proto:390

Used in: ActionExecuted, BuildToolLogs, NamedSetOfFiles, TargetComplete, TestResult, TestSummary

message NamedSetOfFiles

build_event_stream.proto:406

Payload of a message to describe a set of files, usually build artifacts, to be referred to later by their name. In this way, files that occur identically as outputs of several targets have to be named only once.

Used in: BuildEvent

message OptionsParsed

build_event_stream.proto:320

Payload of an event reporting on the parsed options, grouped in various ways.

Used in: BuildEvent

message OutputGroup

build_event_stream.proto:449

Collection of all output files belonging to that output group.

Used in: TargetComplete

message PatternExpanded

build_event_stream.proto:360

Payload of the event indicating the expansion of a target pattern. The main information is in the chaining part: the id will contain the target pattern that was expanded and the children id will contain the target or target pattern it was expanded to.

Used in: BuildEvent

(message has no fields)

message Progress

build_event_stream.proto:225

Payload of an event summarizing the progress of the build so far. Those events are also used to be parents of events where the more logical parent event cannot be posted yet as the needed information is not yet complete.

Used in: BuildEvent

message TargetComplete

build_event_stream.proto:463

Payload of the event indicating the completion of a target. The target is specified in the id. If the target failed the root causes are provided as children events.

Used in: BuildEvent

message TargetConfigured

build_event_stream.proto:377

Payload of the event indicating that the configurations for a target have been identified. As with pattern expansion the main information is in the chaining part: the id will contain the target that was configured and the children id will contain the configured targets it was configured to.

Used in: BuildEvent

message TestResult

build_event_stream.proto:505

Payload on events reporting about individual test action.

Used in: BuildEvent

message TestResult.ExecutionInfo

build_event_stream.proto:536

Message providing optional meta data on the execution of the test action, if available.

Used in: TestResult

message TestResult.ExecutionInfo.ResourceUsage

build_event_stream.proto:564

Used in: ExecutionInfo

message TestResult.ExecutionInfo.TimingBreakdown

build_event_stream.proto:557

Represents a hierarchical timing breakdown of an activity. The top level time should be the total time of the activity. Invariant: time_millis >= sum of time_millis of all direct children.

Used in: ExecutionInfo

enum TestSize

build_event_stream.proto:365

Enumeration type characterizing the size of a test, as specified by the test rule.

Used in: TargetComplete, TargetConfigured

enum TestStatus

build_event_stream.proto:492

Used in: TestResult, TestSummary

message TestSummary

build_event_stream.proto:576

Payload of the event summarizing a test. TODO(aehlig): extend event with additional information as soon as we known which additional information we need for test summaries.

Used in: BuildEvent

message UnstructuredCommandLine

build_event_stream.proto:315

Payload of an event reporting the command-line of the invocation as originally received by the server. Note that this is not the command-line given by the user, as the client adds information about the invocation, like name and relevant entries of rc-files and client environment variables. However, it does contain enough information to reproduce the build invocation.

Used in: BuildEvent

message WorkspaceStatus

build_event_stream.proto:340

Payload of an event reporting the workspace status. Key-value pairs can be provided by specifying the workspace_status_command to an executable that returns one key-value pair per line of output (key and value separated by a space).

Used in: BuildEvent

message WorkspaceStatus.Item

build_event_stream.proto:341

Used in: WorkspaceStatus