New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 679234 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Waterfall pages: make it clear which bots are actually tree closers

Project Member Reported by dsansome@chromium.org, Jan 9 2017

Issue description

From https://docs.google.com/document/d/1W1FUz2-bvi1Ko19O2qjHmmZhwhewvRReJ8KViHk-sNA/edit#

It should be more obvious which builders will cause the tree to be closed if they go red.
 
Is this a sheriff-o-matic bug, rather? I don't maintain gatekeeper or the waterfall pages. There are probably better owners for those. 
Cc: seanmccullough@chromium.org
Owner: jparent@chromium.org
Hmm, the only mention of "gatekeeper" on go/chrome-infra-services had your name against it, but that's for alerts-dispatcher:  https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/services.md#alerts_dispatcher

Ok, over to Julie to find an owner!
Owner: martiniss@chromium.org
Gatekeeper ... Mr. Martiniss?
Owner: seanmccullough@chromium.org
I'm no longer gatekeeper, so back to sean! :)
Cc: vadimsh@chromium.org dpranke@google.com
it would be great if we could express whether a builder is a tree closer or not, in a new skylark config. Then this bug would be easier to solve, and we could display the "closer" bit at the Milo level.

Sign in to add a comment