Hi there, just a quick request for comments on feasibility for the attached mockup (with lots of improbable figures). It's still ugly of course.
The goal is to have a high-level report of the whole chain of building the distribution, step by step to visually advocate: * checkpoints along the process to be implemented progressively and reported as such; * some sort of a continuous integration/test/build cycle; * what it takes to make a distribution. There are certainly totally fake/useless figures named there and others misreported that would show a misunderstanding of the processes at hand. And there are too missing figures. Feel free to correct (and suggest why/where/how to get those values). And of course, some blocks suggest existing, deeper level reports or processes; that's the point of identifying those needed/existing and putting them all together. Romain
Mockup!
Mageia factory status dashboard
This document aggregates various reports from Mageia build chain, from source code to shipped test ISOs.
Upstream Projects
- 32 in mageia/soft, view svnweb
- 2343 in other places
- 143 out of sync with upstream
view detailed report
Source Packages
Status: OK.
- 2.1GB
- 4325 packages
- 23 orphans
- 432 out-of-upstream-sync
- 432 patches
- 234 open bugs on 43 packages
- 54 rpmlint errors in 23 packages (5%)
- 5433 rpmlint warnings in 3325 packages
view svn, git, detailed report
Packages Build (past 24 hours)
Status: READY.
- 5 nodes working out of 6
- used 78% of the time
- queue size: 0/20/4
- built time: min/max/avg
- wait time: min/max/avg
- 1234 built packages
- 321 not built (%):
- missing dependencies %
- other
view pkgsubmit, detailed report
Cauldron Compiled Packages
Status: NOT READY.
- 9.2GB
- 4324 packages
- Broken hdlist (i586/nonfree)
- Signatures: 23 missing (i586/nonfree, i586/tainted)
- Dependencies: 32 missing, 2 circular
- 15 packages are not in sync with their source
- 432 missing/broken signatures
- 213 bugs
- @todo: per package test suite? rpmlint, other
- @todo: src => 32/64/arm
- Basesystem size: 437MB, w/o suggests: 163MB
view repository, detailed report
- how to visualize several trees at once? (stable & cauldron at least)
Cauldron ISO Build / QA / Publication (past 3 days)
Status: READY, OK.
Built packages tree is not ready – no build planned.
Or:Next build 1a1 should start in about 12 hours (at 2011-03-15-20:23:33), with a new context.
Or:Build 1a0 (context diff w/ build 199) – 2011-03-14 23:03:15
- DVD i586, build ok (log), tests failed (log), cauldron-2-dvd-i586-1a0-qafail.iso
- DVD x86_64, build ok (log), tests ok (log), cauldron-2-dvd-i586-1a0-ok.iso
- CD dual, build failed (log)
- building netinstall image...
Build 199 (context diff w/ build 198) – 2011-03-12 23:03:15
Item Build Tests Download DVD i586 OK (log) OK (log) cauldron-2-1a0-dvd-i586-ok.iso DVD x86_64 OK (log) FAILED (log) cauldron-2-1a0-dvd-x86_64-qafail.iso CD dual FAILED (log) netinstall OK (log) OK (log) cauldron-2-1a0-netinstall-ok.iso
Notes. Successfully built ISOs are automatically tested (view ISO QA docs) and pushed to isos.mageia.org/daily. Failed ISOs are kept for review. All ISOs are dropped after 7 days of age.
- A "context" is the whole context of an ISO build: packages tree status, particular config status.
- Not sure about the layout for a build result: list or table?
Essayer : droite/gauche (renversé), haut/bas (renversé) pour mettre le focus (premier item lu en haut à gauche) soit sur le résultat (les ISOs) soit sur la source.
Search
Have a search for packages infos + high-level report matrix.
indexhtml
- upstream: ... version
- source size
- spec file OK
- maintained by rda, ennael
- no patch
- 2 bugs
- 2 rpmlint warning
- License
- built version ... in 2 minutes (log)
- last rebuilt on ...
- Needed by: evolution (needs rebuild), firefox (needs rebuild)
- RPM: noarch: 230kB
- in core
- in hdlist
- signature OK
- dependencies OK
