[Qa-jenkins-scm] [jenkins.debian.net] 01/01: improve logical order

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit be7db48f249ac89f44435f4cc16c76c2084ac2de
Author: Holger Levsen <holger at layer-acht.org>
Date:   Wed Jul 8 12:48:40 2015 +0200

    improve logical order
---
 README | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README b/README
index c338750..163385f 100644
--- a/README
+++ b/README
@@ -140,7 +140,6 @@ Installation tests inside chroot environments.
 
 * Currently, three suites are tested on amd64: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' using link:https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain[our toolchain] through eight concurrent builder jobs which are each constantly testing packages and saving the results of these tests.
 
-* There are 3 jobs testing the link:http://www.coreboot.org/[coreboot], link:https://openwrt.org/[OpenWrt] and link:http://www.netbsd.org/[NetBSD] projects. The results of the tests can be seen respectively at https://reproducible.debian.net/coreboot/, https://reproducible.debian.net/openwrt/ and https://reproducible.debian.net/netbsd/.
 
 * 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. New packages" in this context means:
 ** truly new packages (either uploaded to 'unstable' or 'experimental' or migrated to 'testing'),
@@ -156,7 +155,7 @@ Installation tests inside chroot environments.
 
 * Then there are two more jobs to create sid and testing schroots to run debbindiff on the the two results. This is necessary since to investigate haskell binaries, debbindiff needs access to the same haskell compiler version as the investigated packages have been built with.
 
-* Finally, there is a maintenance job running every 4h, making sure things are considerably under control.
+* For making sure things are considerably under control at any time, there is a maintenance job running every 4h, mostly doing cleanups.
 
 * The jenkins job overview at https://jenkins.debian.net/view/reproducible/ probably makes it clearer how the job scheduling works in practice.
 
@@ -174,6 +173,8 @@ jenkins at jenkins:~$ /srv/jenkins/bin/reproducible_blacklist.sh $suite $package1
 
 * Job configuration is at the usual location for 'jenkins.debian.net' - there's a 'job-cfg/reproducible.yaml' defining all the jobs and lots of scripts in 'bin/reproducible_*.(sh|py)', plus a few config files like for 'sudo' or 'apache2'.
 
+* Finally, there are also three jobs testing the link:http://www.coreboot.org/[coreboot], link:https://openwrt.org/[OpenWrt] and link:http://www.netbsd.org/[NetBSD] projects. The results of the tests can be seen respectively at https://reproducible.debian.net/coreboot/, https://reproducible.debian.net/openwrt/ and https://reproducible.debian.net/netbsd/.
+
 === dvswitch jobs
 
 * There are three jobs currently:

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git