782771 - release sanity should ensure all necessary slaves are connected to master

Status: RESOLVED WONTFIX

(Release Engineering :: Release Automation, defect, P3)

Description

[[e-mail] (:bhearsum)]

Right now we have a manual checklist item that tells us to make sure we have enough slaves of each platform connected to a master before starting the release. We should be able to get release sanity to do this automatically. It would need to check that we have at least 1 of each en-US slave available and at least 1 (possibly more than one) of each l10n slave available. In an ideal world we'd check every single builder, but that's probably overkill for now since just checking en-US + l10n would cover everything.

Pseudo code for what to do in release sanity is here (minus the glue in the __main__ section: https://github.com/bhearsum/tools/commit/1e781fa35fedc32018d3d58006ba213bce1e35ff

We also need to move https://github.com/mozilla/buildbotcustom/blob/master/process/release.py#L102 to tools/lib/python/release/names.py and have it take sourceRepoInfo['name'] as an argument, to avoid duplicating that logic.

Easy!

Comment 1

[[e-mail] (:bhearsum)]

bug 710312 might make this unnecessary.

Comment 3

[[e-mail] (:bhearsum)]

Yeah, this isn't useful now that in a multimaster world.