Stacked console view, with index_builder, to replicate go/legoland |
||||||
Issue descriptionCrOS has a need to display 88 builders for Post-submit builds and ~140 builders for Release builds. See go/legoland as an example of how this is rendered today. We need an equivalent “high-density mode” in which builders can still be grouped by categories but with wrapping such that one doesn’t have to scroll all the way to the right like in the old Buildbot waterfall. This item tracks implementing this feature in Milo.
,
Nov 9
ah, from reading bug 903493, it seems you don't really need columns in the top, but rather 140 named boxes in a [row associated with a commit], potentially overflowing.
,
Nov 9
Right. Generally speaking, we need to be able to see the names of the builders in the high density mode.
,
Nov 13
,
Nov 15
how many of 140 post-commit builders are critical? if we had one console for critical and one for non-critical, how wide would that be? Where can I see the list of 140 builder names?
,
Nov 15
Here is a view of the current release builders. https://cros-goldeneye.corp.google.com/chromeos/legoland/builderSummary?builderGroups=release&limit=1&buildBranch=master
,
Nov 16
On the link that Don provided, the greyed out ones are non-critical. Names are there too. If we had one console for each, it would be too wide: you'd have to scroll-left-to-right. We're working on bringing the post-submit builders up right now so don't have that in the UI yet.
,
Dec 19
,
Jan 15
From an offline discussion yesterday, this can be augmented in the existing console view (as a separate view) with about 3 changes: * Allow stacked builder bubbles in the rows, hiding builder summaries * Export "master-run" information for child builds in the source_manifest * Introduce index_builder, where we determine rows by builder history rather than gitiles.
,
Jan 15
,
Jan 15
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by no...@chromium.org
, Nov 9