Config CrOS to emit SoM alerts for parent builder failures |
||
Issue descriptionThis item tracks the actual re-integration with SoM from the CrOS side. Previously, we used a special “builder” to extract information about the failed builds and export them to SoM--though, not in a format that was congruent with the content that SoM was configured to render. This time, we should be able to have SoM use the Buildbucket and Milo ChromeOS project data directly, without an explicit export, but some exploration is needed here. In particular, we need to ensure that SoM is only rendering failures for the parent builders on postsubmit and release; not for any of the children (e.g. amd64-generic).
,
Nov 15
SOM might need to switch to go/buildbucket-bq or go/buildbucket-rpc to achieve this. It still uses deprecated Buildbot API because some Chrome builds are still on Buildbot.
,
Nov 16
Sean, is that on the roadmap?
,
Dec 18
Re #4 yes switching to buildbucket is on SoM's roadmap. It has to be, as buildbot is getting turned down in 2019.
,
Jan 9
"parent builders on postsubmit and release" - is there a dedicated buildbucket bucket just for these, or would we need to extract info from elsewhere to separate these from child builds?
,
Jan 9
There will be a dedicated Buildbucket builder for each of these inside of a single bucket, at launch. There will be more buckets starting in Q2.
,
Jan 10
as a project admin, can I configure the list of builders for SOM to watch? This would solve the "not for any of the children" problem.
,
Jan 11
re #8 Today, that configured list of builders to watch is determined by what's in the gatekeeper config files. So if we can describe CrOS's parent builders unambiguously in terms captured by that config file, we may already support this request with a config file change. Note that you needn't actually use gatekeeper in order to have SoM read your gatekeeper configs. |
||
►
Sign in to add a comment |
||
Comment 1 by jclinton@chromium.org
, Nov 13