| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
Change-Id: I55fd5b2f38cad9d2b18d369ae51dbd93c2c92288
PiperOrigin-RevId: 152925304
|
| |
|
|
|
|
|
|
|
|
|
| |
Change the BuildEvent interface to accept a generic class of converters.
In this way, we won't have to change it again in the future, once more
converters are needed. In fact, a new converter is needed right now (will
be added in a follow-up patch) to allow build events to know the name of
named artifact groups already reported in the stream.
Change-Id: Ibb32ea5fff361e21bcf2d34818d8351a1da7a2e3
PiperOrigin-RevId: 152131870
|
| |
|
|
|
|
|
|
|
|
|
|
| |
...through the ExtendedEventHandler. The main use case of the extended
event handler is to allow posting of BuildEvents. So it is implicit that
they are all good to be posted. Declare this.
--
Change-Id: I9fcb2f33e57e05c3a05509b1121e44396f28c168
Reviewed-on: https://cr.bazel.build/9011
PiperOrigin-RevId: 148090465
MOS_MIGRATED_REVID=148090465
|
| |
|
|
|
|
|
|
|
|
|
| |
Bazel-created files (like log files of test runs) are internally reported
as Paths. However, this is not always the most useful representation of the
location of that artifact for a consumer of build events. Therefore, support
a mapping of paths to more useful URIs.
--
PiperOrigin-RevId: 144843525
MOS_MIGRATED_REVID=144843525
|
|
|
Bazel in the will provide a machine-readable stream of important build
events. These interfaces set up the framework and expectations about
the produced events and the entities distributing those events.
--
Change-Id: If2c3b2e11c31b0136b57eadeef2d2f8f8fe5e2e7
Reviewed-on: https://bazel-review.googlesource.com/#/c/6272
MOS_MIGRATED_REVID=134522369
|
Klaus Aehlig