public non-virtual ppas are unnecessarily limited on builders per architecture
Bug #666308 reported by
LaMont Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Colin Watson |
Bug Description
Given that all non-virtualized ppas are operating within the same scope and trust model as the main archive, they should all be allowed to take 100% of the builders for a given architecture.
It would be nice to override the above permissions on a per-ppa basis, in case I need to lart someone for abuse. That can be done outside of launchpad though. Long term, it would be nice to have the ability for a launchpad admin (not the ppa owner or mere archive admin) to specify a maximum percentage, as well as a minimum number (overriding maximum - maximum == 75%, minimum=2 would give the ppa up to 2 machines on architectures with 2 or 3 builders)
thanks,
lamont
Related branches
lp:~cjwatson/launchpad/remove-ppa-builder-limits
- William Grant (community): Approve (code)
-
Diff: 120 lines (+9/-61)2 files modifiedlib/lp/buildmaster/tests/test_builder.py (+7/-17)
lib/lp/soyuz/model/buildpackagejob.py (+2/-44)
Changed in soyuz: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: ppa trivial |
summary: |
- non-private non-virtualized ppas should be allowed more builders per - architecture + public non-virtual ppas should be allowed more builders per architecture |
summary: |
- public non-virtual ppas should be allowed more builders per architecture + public non-virtual ppas are unnecessarily limited on builders per + architecture |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
A feature rule could do this -really- easily. Per-user / group
certainly, possibly per-ppa too (though we don't really have a
'current ppa' concept in the app container.