From Fedora Project Wiki
< User:Skvidal | BuildSystem
(→UI Requirements) |
|||
| Line 17: | Line 17: | ||
== NON-UI (rest-ish) requirements == | == NON-UI (rest-ish) requirements == | ||
| + | |||
| + | |||
| + | |||
| + | == backend process requirements/design == | ||
| + | === master process which spins off builds === | ||
| + | * count of number of builders it can make | ||
| + | * way to make new ones and to destroy old ones | ||
| + | * place to store the results | ||
| + | * url schema for referring to its own repos from "the world" | ||
| + | |||
| + | === pruning repos === | ||
| + | * policy on how long things are kept | ||
| + | * handles exclusions/exceptions | ||
| + | * warns on removals N days in advance and repeatedly | ||
| + | |||
| + | === repo editing/managing === | ||
| + | * handle requests from ui to delete from a repo and rebuild repodata | ||
| + | * handle requests to modify repodata (add group file, for example) | ||
Revision as of 17:20, 2 August 2012
Contents
BuildSystem Specs
This is where we will put the specs for the web interface we need to build
DB Schema
UI Requirements
Basic original requirements for personal repos:
- auth to fas
- data to get:
- name of repo
- srpms to build (urls to them)
- urls to the repos to use for other build deps
- base fedora/rhel tree to build from
- some way to query this data from the build manager
NON-UI (rest-ish) requirements
backend process requirements/design
master process which spins off builds
- count of number of builders it can make
- way to make new ones and to destroy old ones
- place to store the results
- url schema for referring to its own repos from "the world"
pruning repos
- policy on how long things are kept
- handles exclusions/exceptions
- warns on removals N days in advance and repeatedly
repo editing/managing
- handle requests from ui to delete from a repo and rebuild repodata
- handle requests to modify repodata (add group file, for example)