Comment 8 for bug 393546
Revision history for this message
| Michael Bienia (geser) wrote Re: Super-low priority option for automated PPA builds | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
What about limiting that a PPA can only use one buildd per arch at a time? That way an upload of a long-running build for several series won't occupy all available buildds for an architecture at the same time but build them one after another.
IMHO it's fair to expect that someone (or a team) uploading a huge amount of package in short time has to wait a little bit to get them all build. If the packages are build fast that shouldn't introduce a huge extra delay (depending on the queue of course) and long-builds won't take all available buildds.
Of course a small number of teams doing daily-builds will still be able clog the buildds but they all have the same rights to use them as any other PPA user.
An other option would be that a certain amount of buildds is reserved for the "general" use and not used by the daily upload builds. That way "normal" PPA user have a chance to get their package build in a timely manner.
Which option is more preferable depends also on the usage rate of the buildds. Are there any statistics about it (what part of a day are they building or waiting for jobs)?