413728 - merge 1.8/1.9 automation buildbot masters

Status: RESOLVED DUPLICATE of bug 417058

(Release Engineering :: General, defect, P3)

Description

[Robert Helmer [:rhelmer]]

Currently we have four buildbot masters for release automation:

staging-1.8-master
production-1.8-master
staging-1.9-master
production-1.9-master

Each of these also runs a slave (usually called "console" either formally or informally) which does tagging, source, and stage steps (builds are uploaded to the master for the benefit of the stage step).

We should merge these into one production and one staging master, and move the slaves off. This requires some changes to automation, at least:

* tagging/source/stage should run on the linux buildslave
* builds should be uploaded somewhere else
** perhaps directly to stage.m.o, and have the stage factory create the private staging area by downloading from there instead of assuming it can copy

Then the master will be just a master, and we can use categories to separate various branches and nightly builds.