make the following happen:
- buildbucket sends input to kitchen in a form of buildbucket.v2.Build message
- kitchen sends output back to buildbucket in a form of buildbucket.v2.Build message, a subset thereof. Not annotation.proto.
- kitchen sends output via direct RPCs to buildbucket (not logdog, not pubsub, not isolate) each time there is something new (e.g. new step)
this moves some responsibilities from buidbucket to kitchen, including (annotation.proto -> Build) conversion. This removes annotation.proto from buildbucket<->kitchen protocols. kitchen will encapsulate annotations. This also removes recipe-specific, kitchen-specific stuff from the protocol.
This establishes a generic protocol for potential alternative "build executors", e.g. like an appengine app that executes a build in a special way (FindIt's "Virtual tester", DM), or something on a bot, but not a recipe.
This is prerequisite for real-time step info ( issue 843714 ).
Design TBD.
make the following happen:
- buildbucket sends input to kitchen in a form of buildbucket.v2.Build message
- kitchen sends output back to buildbucket in a form of buildbucket.v2.Build message, a subset thereof. Not annotation.proto.
- kitchen sends output via direct RPCs to buildbucket (not logdog, not pubsub, not isolate) each time there is something new (e.g. new step)
this moves some responsibilities from buidbucket to kitchen, including (annotation.proto -> Build) conversion. This removes annotation.proto from buildbucket<->kitchen protocols. kitchen will encapsulate annotations. This also removes recipe-specific, kitchen-specific stuff from the protocol.
This establishes a generic protocol for potential alternative "build executors", e.g. like an appengine app that executes a build in a special way (FindIt's "Virtual tester", DM), or something on a bot, but not a recipe.
This is prerequisite for real-time step info ( issue 843714 ) and indexing by commit position (issue 851585)
Design TBD.
Comment 1 by no...@chromium.org
, Jun 16 2018