Commit 0b084efe authored by Holger Levsen's avatar Holger Levsen

reproducible: be more verbose

parent 9068867d
......@@ -123,9 +123,13 @@ Installation tests inside chroot environments.
* Several jobs are being used to assemble the website https://reproducible.debian.net which is actually a collection of static html and log files (and very few images) being served from this host. Besides the logfiles data is stored in an SQLite database which can be downloaded from https://reproducible.debian.net/reproducible.db. (That copy is updated every four hours.)
* Currently, three suites are tested on amd64: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' through four builder jobs, alpha, beta, gamma and delta, which are each re-started every two minutes.
* The (current) purpose of https://reproducible.debian.net is to show the prospects of reproducible builds for Debian. IOW: this is research, showing what could (and should) be done... check https://wiki.debian.org/ReproducibleBuilds for the real status of the project!
* Packages to be build are scheduled via a scheduler job, which runs every hour and which schedules new packages to be tested if the queue is below a certain threshold.
* Currently, three suites are tested on amd64: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' through four builder jobs, alpha, beta, gamma and delta, which are each constantly testing packages and saving the results of these tests.
* The jenkins job overview at https://jenkins.debian.net/view/reproducible/ probably makes it clearer how the job scheduling works in practice.
* Packages to be build are scheduled in the SQLite database via a scheduler job, which runs every hour and which schedules new packages to be tested if the queue is below a certain threshold.
* Several other jobs exist to build the html pages and to create a JSON file which can be downloaded from https://reproducible.debian.net/reproducible.json.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment