This page is a To Do list for test.reproducibile-builds.org
Documenting+Improving set up
- add documentation for setting up tests.r-b.org testbed to git!
- many shell scripts expect directories to be created before them (they should make them selves!)
- convert bin/reproducible_html_pkg_sets.sh into python
- convert bin/reproducible_html_dashboard.sh into python
- debian: common navigation (using left side navi menu like on the debian pkg pages), but different themes for dashboards, indexes and package pages
- improve the intro texts:
- explain status in plain english on each dashboard, plus add an "executive summary about reproducible builds in the free software world"
- document in the non-debian pages, when we don't have a clear idea yet, how to record+reproduce the build environment and that this is essential for reproducible builds too.
- common code base for creating the webpages for debian|coreboot|openwrt|netbsd|archlinux|fedora
- convert python scripts to pthon modules, DRY up code
- test results from different projects should be presented in similar ways (extend the bin/reproducible_*.py scripts that create the debian web pages -- first we need to fix db)
- bin/reproducible_$foo.sh scripts should only record results to db, not build websites
- Remove manual built SQL queires from .py scripts -- replace with aqlalchemy
- Migrate from SQLite to Postgres
- Better schema design
- Add results from other distros to reproducible.db
- Should be able to compare status of same package across different architectures
- Should be able to compare status of same package across different distributions
- schema will have to be adapted for non-packaged based projects (like BSD's base system)
- reproducible_schema.svg in jenkins.d.n.git is currently out of date
- also we dont store package set membership in the db, but just with files in the filesystem.
- Reduce code duplication in the backend: while always being different, tests for different projects share a good amount of logic. Ideally adding a new project—e.g. testing Tor Browser—should not require writing more than a couple shell scripts and adding the right jobs to Jenkins.
- Get more value out of the database: some of the content of the .buildinfo files could be recorded in the database, helping to understand what changes made a package (un)reproducible. Other projects than Debian might also benefit from recording the history.