This is a master tracking bug for improvements to ci.chromium.org/console. Individual bugs tracking each request will be opened against this one.
ci.chromium.org’s console high-level overview of builder success/failures lacks feature parity with the same view that we have today at go/legoland. This request is to achieve parity
increased density so that we can show all 88 or 140 builders in the Post-submit/Release categories,
* sorting “master” builders to the left of those groups,
* “greying out” builders based on some property/tag in the Buildbucket build (e.g. critical/non-critical),
* showing a configurable set of changes for each builder defaulting to only 3 (instead of the current change-based window default of 25), and
*allowing users to configure which categories they want to view (as opposed the view being static).
CrOS may contribute some UI eng resources depending on need.
This view is primarily of interest to Infra folks and tree guardians. Regular CrOS contributors shouldn’t be using this page.
This is a master tracking bug for improvements to ci.chromium.org/console. Individual bugs tracking each request will be opened against this one.
ci.chromium.org’s console high-level overview of builder success/failures lacks feature parity with the same view that we have today at go/legoland. This request is to achieve parity:
* increased density so that we can show all 88 or 140 builders in the Post-submit/Release categories,
* sorting “master” builders to the left of those groups,
* “greying out” builders based on some property/tag in the Buildbucket build (e.g. critical/non-critical),
* showing a configurable set of changes for each builder defaulting to only 3 (instead of the current change-based window default of 25), and
*allowing users to configure which categories they want to view (as opposed the view being static).
CrOS may contribute some UI eng resources depending on need.
This view is primarily of interest to Infra folks and tree guardians. Regular CrOS contributors shouldn’t be using this page.
This is a master tracking bug for improvements to ci.chromium.org/console. Individual bugs tracking each request will be opened against this one.
ci.chromium.org’s console high-level overview of builder success/failures lacks feature parity with the same view that we have today at go/legoland. This request is to achieve parity:
* increased density so that we can show all 88 or 140 builders in the Post-submit/Release categories,
* sorting “master” builders to the left of those groups,
* “greying out” builders based on some property/tag in the Buildbucket build (e.g. critical/non-critical),
* showing a configurable set of changes for each builder defaulting to only 3 (instead of the current change-based window default of 25), and
* allowing users to configure which categories they want to view (as opposed the view being static).
CrOS may contribute some UI eng resources depending on need.
This view is primarily of interest to Infra folks and tree guardians. Regular CrOS contributors shouldn’t be using this page.
Comment 1 by jclinton@chromium.org
, Nov 8