Communications channel for parent to children |
||||
Issue descriptionThis bug tracks establishing a communications channel from parent to child scripts. This is related to the Stable Build API <https://docs.google.com/document/d/1-UwZUs2tjhxEiPXQDfUw-AcNH0rVT7g4on-6li-XslI/edit> problem area but not quite the same.
,
Nov 29
,
Nov 30
Relevant discussion: https://docs.google.com/a/google.com/spreadsheets/d/1RQi9-i_J6neF6JyIcWAJXbzMG1qQrnjuw72hNjFY648/edit?disco=AAAACTqZ-l0 I think the end realization was that we don't need a communication channel, sending data over the build.proto is sufficient, and where the data is too large it can be put in Isolate and sent as a link.
,
Dec 5
Current POR is for the CQ service to trigger all builds, obviating this work.
,
Dec 5
This bug was tracking scripts communication strategy, not builders. E.g. from Recipes to Chromite either through stdin/stdout serialized data structures or a gRPC server if that ever becomes needed.
,
Dec 5
> This bug was tracking scripts communication strategy, not builders. The summary is "Communications channel for parent to children"... It sounds like we need a bug for "Stable Build API"; would that cover what you are thinking of?
,
Dec 5
Yep, sounds good.
,
Dec 5
|
||||
►
Sign in to add a comment |
||||
Comment 1 by jclinton@chromium.org
, Nov 29