QA dashboard for upstream projects
Review the current state of QA dashboard for upstream projects.
Review the metrics we want and sync with the latest status of lp:cupstream2distro.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Martin Mrazik
- Direction:
- Needs approval
- Assignee:
- Martin Mrazik
- Definition:
- Approved
- Series goal:
- Accepted for raring
- Implementation:
-
Started
- Milestone target:
-
ubuntu-13.04-month-5
- Started by
- Martin Mrazik
- Completed by
Whiteboard
Acceptance criteria:
- qa dashboard is deployed and accessible
- all projects defined in lp:cupstream2distro-config (which is all our projects) are displayed in the dashboard and you can find -- test coverage, internal package tests status (# of tests, pass rate), coverity status
- per stacks as defined in lp:cupstream2distro-config -- status of the daily release (pass/fail rate)
Work Items
Work items for ubuntu-
[mrazik] : schedule a regular cadence for planning (weekly/
[mrazik] : create a meaningful backlog for project planning (especially post March-2013): DONE
[allanlesage] : adapt existing multiconfiguration models/import process to new cu2d-config downstream-job model/process : INPROGRESS
[fginther] : View for projects within a stack : INPROGRESS
[allanlesage] : Associate jenkins jobs with a release-
[mrazik] : Jenkins ci/autolanding jobs for helipad : INPROGRESS
[allanlesage] : import existing data to production DB, babysitting and bugfixes as necessary : INPROGRESS
Work items for ubuntu-
visualize coverage at the stack level (i.e. exposing coverage of dependent projects) : TODO
developer documentation: how to set up, hack with, links for helpful Django docs, etc. : TODO
View for the list of stacks : TODO
staging deployment script : TODO
Aggregate junit and coverage data for all release-
