buildd admins should be able to adjust Archive.relative_build_score

Bug #1002387 reported by Colin Watson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Colin Watson

Bug Description

https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-buildds-usage requests the ability for buildd admins to be able to adjust the relative build score of an archive over the API. As with packagesets (bug 990219), this makes sense because build scores mediate access to a global resource (the build farm), which buildd admins are supposed to be responsible for running.

Right now, Archive.relative_build_score can be set in the UI by admins or commercial admins, I'm guessing because it was mainly there for P3As (bug 382804 doesn't really make it clear). I'm not that interested in buildd admins having UI access to this - that would be fiddly because we'd need a sort of reduced variant of +admin for them - but I would like to expose this field over the API and allow any of admins, commercial admins, and buildd admins to modify it.

Tags: qa-ok

Related branches

Colin Watson (cjwatson)
Changed in launchpad:
status: New → In Progress
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Colin Watson (cjwatson) wrote :

launchpad-buildd-admins, admins, and commercial-admins can all now modify relative_build_score. Random users and archive owners without other relevant privileges cannot.

tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.