New issue
Advanced search Search tips

Issue 796662 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Shut down the chromium.chrome waterfall

Project Member Reported by dpranke@chromium.org, Dec 20 2017

Issue description

We should shut down the chromium.chrome waterfall; it's mostly redundant with official.desktop.continuous, and we shouldn't be doing public builds with chrome_branded=true and src-internal checked out.

Rather than migrate it to LUCI, we should just shut it down :).

One catch, however, is that we should make sure we don't lose the sheriff coverage of this configuration. This means we should fix bug 632162 and make sure at least official.chromium.continuous failures on trunk show up in sheriff-o-matic.
 
Status: Available (was: Untriaged)
Owner: ----
I'm not sure if/when I might have time to work on this, so I'm going to disclaim ownership, and someone else can pick it up as part of the LUCI migration.

Comment 3 by efoo@chromium.org, Feb 28 2018

Labels: LUCI-Backlog LUCI-Blocker-Chromium

Sign in to add a comment