New issue
Advanced search Search tips

Issue 903493 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: 1
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature

Blocked on:
issue 903491

Blocking:
issue 903488


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Allow projects to change the default number of rows to render on the console (3 for CrOS); allow more granular than 25/50/100/200

Project Member Reported by jclinton@chromium.org, Nov 8

Issue description

If we enable a high-density mode (issue 903491), then we’ll also need to decrease the number of changes shown for each builder. This should be configurable on a per-project basis. Since CrOS will be interested in much smaller numbers of changes on the Console view, allowing granular changes to the number of changes shown would also be good. For example, many people only show the last two builds since they are only interested in “what’s going on right now”.
 
Labels: Disable-Nags
Cc: no...@chromium.org
Owner: hinoka@chromium.org
Status: Assigned (was: Available)
i think it should be a setting of a console (defined in a project), that's where all console configuration is defined today.
Sounds fine.
EstimatedDays: 2
This sounds like an alternative view to the builder view we currently have (rather than a console, since we're interested in builds relative to time rather than commits)
https://ci.chromium.org/p/chromium/g/main/builders

EstimatedDays: 1
Summary: Allow projects to change the default number of rows to render on the console (3 for CrOS); allow more granular than 25/50/100/200 (was: Implement allowing a per-project default number of changes to render (3 for CrOS); allow more granular than 25/50/100/200)
Blockedon: 903491
Depending on how the stacked view looks, we may or may not need this.
Labels: Pri-1

Sign in to add a comment