BEP: Add tags and output files to TargetComplete event

A target's tags and output files are reported as part of
the TargetComplete event of the build event protocol (BEP).

The output files are grouped by their corresponding output
group. If an output file belongs to more than one output group
it appears once in each output group.

--
Change-Id: Ia37db68709850d8550e478dcc30064dc7366bd1b
Reviewed-on: https://cr.bazel.build/8955
PiperOrigin-RevId: 148667599
MOS_MIGRATED_REVID=148667599

1 files changed, 17 insertions, 0 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/build_event_stream.proto b/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/build_event_stream.proto
index fc50d9b358..f70c715781 100644
--- a/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/build_event_stream.proto
+++ b/src/main/java/com/google/devtools/build/lib/buildeventstream/proto/build_event_stream.proto
@@ -198,11 +198,28 @@ message ActionExecuted {
   string label = 5;
 }
 
+// Collection of all output files belonging to that output group.
+message OutputGroup {
+  // Name of the output group
+  string name = 1;
+
+  // List of output files that belong to this output group.
+  repeated File output_file = 2;
+}
+
 // 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.
 message TargetComplete {
   bool success = 1;
+
+  // The output files are arranged by their output group. If an output file
+  // is part of multiple output groups, it appears once in each output
+  // group.
+  repeated OutputGroup output_group = 2;
+
+  // List of tags associated with this target.
+  repeated string tag = 3;
 }
 
 // Payload on events reporting about individual test action.