Gardening chrome on chromeos is challenging at the best of times. We are hoping to rally around SoM to build gardening tools, however without access to the internal waterfalls SoM is not very useful for gardening.

In particular the pfq-informational builders which usually reveal chrome on chromeos failures first are split between https://build.chromium.org/p/chromiumos.chromium/waterfall and https://uberchromegw.corp.google.com/i/chromeos.chrome/waterfall, so having access to just the chromiumos.chromium is confusing at best).

Sean, I am assigning this to you for now to ask the pertinent questions and help drive this effort.

Sean, you mentioned that there was additional information required for this, can you list the details we need to move this forward?

Which vlan is your internal master running on?

akeshet@ can you answer comment #4 or reassign?

Go ahead and reassign to me once answered, thanks!

Comment #4 I don't know. You mean waterfall master? The chrome infra team handles that for us, so perhaps you can answer the question.

+benhenry@ - I know chrome infra is swamped but this has been blocking us for a while now. It sounds like someone needs to do a bit of digging but I'm not sure who that person should be.

Your masters are on vlan 2. See https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave/+/master/gatekeeper_trees_chromeos.json, and how the master names start with master2a and 2b.

In order to get the data, you need to run a copy of alerts-dispatcher, which will poll your buildbot masters, and then upload the data to sheriff-o-matic.

Look at https://chrome-internal.googlesource.com/chrome/tools/build.git/+/master/masters/master.official.infra.cron/builders.pyl (and the associated CLs I wrote to set that up) for how to set this up.

You might also need to modify the alerts dispatcher code to poll your masters directly, since it tries to talk to Chrome Build Extract first, before polling masters, and it currently uses a whitelist to decide what to poll (in https://chromium.googlesource.com/infra/infra/+/master/go/src/infra/monitoring/client/client.go#220). 

Once you have that builder up and running, it should be fairly simple to get the data showing up on the new sheriff-o-matic frontend (live at https://sheriff-o-matic-staging.appspot.com. We still need to move this to prod).

I don't think I have time to do all of this, sadly, but tiffany or sean or someone else might.

Assigning to Tiffany.

I'm working on this now.

(assigning milestones)

Ping - please provide an update to your high priority bug. This bug is stale. Is it really P-1?

I haven't worked on this in a long time.

Sean, someone else has been doing work on ChromeOS, right?

Yes, you may be able  to resolve this as a duplicate of issue 639901 at this point, although there may (or may not) be additional work to do to add builders from the following waterfalls to SoM:

https://chromegw.corp.google.com/i/chromeos.chrome/waterfall

https://build.chromium.org/p/chromiumos.chromium/waterfall

Assigning back to Sean to see if this bug can be closed or not.