We've already implemented this: https://uberchromegw.corp.google.com/i/chromeos.branch/builders . You can see when the next branch build is scheduled on the right-handle column. Currently the sheriffs are ignoring branch builds but I think that it makes sense to ask them to investigate their failures. Do you want to update the sheriff instructions? https://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium-os currently doesn't mench the branch tree at all.

I don't think it makes sense for sheriffs to investigate the failures, since failures found by these runs would be by definition infra issues. Is there an equivalent infra-deputy page?

There's no current capability to do pages: we're building that as a part of CI 2020 with a current anticipated delivery date of Q4.

No, like a web page document =) 
I don't think anyone needs to be paged for weekly background branch builder failures.

It's great that these builders are running already though.

Biggest issue we face with that is that we have no way of knowing which branches are no longer relevant to the business. If we had a way of recording that or finding an owner of the branch when it fails, that would make this more possible.

That's a good point. Would be worthwhile to purge extra branches at some point.

However, most firmware or factory branches that match shipped, non-EOL products are still needed. They don't have owners, or maintainers that could cover for infra issues, other than the infra team.

Of course anyone checking things into the branch in situations where it's generating releases is responsible for not breaking it, but otherwise it's expected to continue working for the life of the product so long as no changes have been checked in.

This was escalated as an SIE Infra request. However, I don't see an action item here.

Removing Infra labels, this is not an infra request. Please re-categorize as appropriate.