Distro buildd usage

Review the buildd resources available for the distro builds and various test builds, discuss buildd uses outside the core distro team (like daily Go builds, and unity test builds).

- priorities for non-distro builds in times when the buildds are needed for distro
- armhf buildd resources. even after stealing armel buildds, the test rebuild did last more than three weeks
- temporary resources for test rebuilds for the whole archive. while main can be done on a weekend, universe takes too long. being able to add two more buildds for amd64/i386 for the time of a test rebuild would help.

Related branches

Related bugs

Sprints

Whiteboard

Near the end of the precise release cycle, the buildds were still quite busy, building non-virtual PPA daily builds for go and unity.

The archive rebuilds also get significantly less capacity due to these daily builds.

The unity team had a hard requirement that every revision be built daily.
Build-failures were avoided by builds in jenkins before landing in trunk.
These builds are used by the developers who need the latest tip everywhere and also copied to a release PPA when sharing for wider testing.
Before this was introduced, there was ARM breakage that went unnoticed.

There are also lots of go builds. Far more than unity, but they do build faster.

There is more buildd hardware on the way for ARM, but that won't entirely solve the problem.

There are now virtualised ARM builders, possibly available.

Priorities:
* Private PPAs get a bump above distro builds: 10000
* Archives can also get a bump

[didrocks] -- conflict on the session, mmrazik is the stackholder for the PS ppa anyway as told at last UDS.