Chromium gerrit should show main waterfall bubbles after the CL lands |
||||
Issue descriptionFlow: * Submit to CQ * CQ bubbles show up * CQ lands change * Plugin identifies which main waterfall build(s) contain this CL, and shows bubbles for them. Use case: since there isn't 100% parity between CQ and main waterfall (and likely never will be), it would be pretty nifty to see your CL's progress through "the entire" system. Once all these bubbles turn green, the likelihood that your CL will be reverted due to waterfall closure is VERY low. Conversely, if the bubbles turn red, you can investigate to see if your CL is a potential cause.
,
Jan 18 2018
This would also simplify the "what tryjobs do we show on the patchset which only exists because the CL was submitted and the commit message changed" problem: we would show the main waterfall jobs instead. Can you point me at the API that I would use to query for builds whose manifest/BoM/whatever contains a particular sha1?
,
Jan 18 2018
That API is kind-of pending until after the migrations are in full swing, but we should definitely collab on this when we have the bandwidth. Milo calculates this information on e.g. https://ci.chromium.org/p/chromium/g/main/console, but doesn't have an API for it. CC'ing nodir who is thinking about more comprehensive API design.
,
Jan 20 2018
I’ve just added “Read affected build“ requirement to go/chops-build-api-prd
,
Yesterday
(46 hours ago)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by iannucci@chromium.org
, Jan 18 2018