REVU autobuilder network
It's been a long suggested feature (for me, on IRC, in #ubuntu-motu) that REVU should have the ability to build packages and make debs available. Implementing this is straight forward once apt-revu exists.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Michael Casadevall
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Needs Infrastructure
- Milestone target:
- None
- Started by
- Michael Casadevall
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Looking into implementing using the Launchpad PPA group revu-buildd
Current Ideas and Specs:
Packages can be uploaded either via normal dput upload, or imported from a PPA. If it is pulled via a dput upload, then an MOTU or Admin has to approve it for building and publishing in the REVU PPA.
This is managed by changing the changelog to create a REVU specific version, with a unique version at the end, and resigning automatically with our own GPG key. A link on the details page will show the build logs of the last uploaded revision.
In cases where the user is copying from PPA, the link will simply point to their own PPA instead of revu-builder, but should Launchpad add support for copying packages from a PPA (it only supports copy-to), REVU should use the Soyuz API to copy packages into our rep to make it so all REVU built packages are in a single location.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
