Private HWPack Builds (11.09 milestone)
Landing Teams work some of the time with code that they can't make public. They do wish to produce hardware packs for evaluating their work, so that they can release them as soon as the member permits it or the license permits it. In order to achieve this landing teams need a system to be able to build hardware packs without exposing them to the world (including other people in Linaro.) offspring.
Blueprint information
- Status:
- Complete
- Approver:
- David Zinman
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
- Implemented
- Milestone target:
- 2011.09
- Started by
- David Zinman
- Completed by
- David Zinman
Related branches
Related bugs
Sprints
Whiteboard
Work Items
Work items:
[salgado] Remove dead code from Offspring: DONE
[salgado] Make it possible to easily run the existing Offspring tests and any new ones we write: DONE
[salgado] Decide whether or not we need to allow users to specify a LP team name to be used as the group of people who have access to a given project: DONE
[salgado] Complete evaluation of alternative ways of restricting access to private stuff and decide which one to use: DONE
[salgado] Refactor django-group-access so that we can use it, without any modifications, in Offspring: DONE
[salgado] Add support for private projects in Offspring models: DONE
[salgado] Add UI for setting ACLs for private projects: POSTPONED
[dooferlad] Add SSH private key storage to database objects (Django and Storm): DONE
[dooferlad] Implement passing SSH private key from master to slave: DONE
[dooferlad] Pass SSH key from slave to builder: DONE
[dooferlad] Builder creates ssh-agent, kills ssh-agent when terminating: DONE
[dooferlad] Builder passes SSH key (from slave) to ssh-agent (ssh-add): DONE
[dooferlad] Add to hwpack specification how to access private hardware packs by specifying the user/token in the archive URL: POSTPONED