1050588 - Report on # of builders added/removed per check-in

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Chris Cooper [:coop] (he/him)]

We're often blindsided by load issues. This load tends to creep up over time, adding a few new tests here and there, until we hit a tipping point where drastic action is required.

I'd like to create a new report that would give us some visibility into when, how, and hopefully why these new builders are being added. There is determinism here. Every time someone checks in code to the relevant repos, we should be checking the list of builders against the builders from the previous revision. *Any delta* should be reported. Where this information should be reported, I'm still not sure.

Since we're struggling with load issues right now, I considered making *adding* builders fatal without some kind of override, possibly enforced by a jenkins test. 

If that's too big a stick, we could have a report that hangs off the slave health page, or a cron job that mails the group when there's a delta.

Are there repos aside from buildbot-configs that we should be tracking here?

Comment 1

[[e-mail] (:bhearsum)]

buildbot is dying!