[Qa-jenkins-scm] [Git][qa/jenkins.debian.net][master] reproducible Debian: update README to reflect the fact that buster is stable

[Holger Levsen]

Holger Levsen pushed to branch master at Debian QA / jenkins.debian.net


Commits:
12a2449e by Holger Levsen at 2021-04-29T18:24:03+02:00
reproducible Debian: update README to reflect the fact that buster is stable

Thanks to Vagrant for noticing! (!MR:102)

Signed-off-by: Holger Levsen <holger at layer-acht.org>

- - - - -


1 changed file:

- README


Changes:

=====================================
README
=====================================
@@ -118,7 +118,7 @@ Installation tests inside chroot environments.
 
 * The (current) purpose of https://tests.reproducible-builds.org is to show the potential of reproducible builds for Debian - and six other projects currently. This is research, showing what could (and should) be done... check https://wiki.debian.org/ReproducibleBuilds for the real status of the project for Debian!
 
-* For Debian, four suites, 'stretch', 'buster', 'unstable' and 'experimental', are tested on four architectures: 'amd64', 'i386', 'arm64' and 'armhf'. The tests are done using 'pbuilder' through several concurrent workers: 40 for 'amd64', 24 for 'i386', 32 for 'arm64' and 55 for 'armhf', which are each constantly testing packages and saving the results of these tests. There's a single link:https://salsa.debian.org/qa/jenkins.debian.net/blob/master/bin/reproducible_build_service.sh[systemd service] starting all of these link:https://salsa.debian.org/qa/jenkins.debian.net/blob/master/bin/reproducible_worker.sh[workers] which in turn launch the actual link:https://salsa.debian.org/qa/jenkins.debian.net/blob/master/bin/reproducible_build.sh[build script]. (So the actual builds and tests are happening outside the jenkins service.)
+* For Debian, five suites, 'stretch', 'buster', 'bullseye', 'unstable' and 'experimental', are tested on four architectures: 'amd64', 'i386', 'arm64' and 'armhf'. The tests are done using 'pbuilder' through several concurrent workers: 40 for 'amd64', 24 for 'i386', 32 for 'arm64' and 55 for 'armhf', which are each constantly testing packages and saving the results of these tests. There's a single link:https://salsa.debian.org/qa/jenkins.debian.net/blob/master/bin/reproducible_build_service.sh[systemd service] starting all of these link:https://salsa.debian.org/qa/jenkins.debian.net/blob/master/bin/reproducible_worker.sh[workers] which in turn launch the actual link:https://salsa.debian.org/qa/jenkins.debian.net/blob/master/bin/reproducible_build.sh[build script]. (So the actual builds and tests are happening outside the jenkins service.)
 ** To shutdown all the workers use:  `sudo systemctl stop reproducible_build at startup.service ; /srv/jenkins/bin/reproducible_cleanup_nodes.sh`
 ** To start all the workers use: `sudo systemctl start reproducible_build at startup.service`
 
@@ -137,7 +137,7 @@ Installation tests inside chroot environments.
 * We would love to have more or more powerful ARM hardware in the future, if you can help, please talk to us!
 
 * Packages to be build are scheduled in the database via a scheduler job, which runs every hour and if the queue is below a certain threshold schedules four types of packages:
-** new untested packages (either uploaded to 'unstable' or 'experimental' or migrated to 'buster' or 'stretch'),
+** new untested packages (either uploaded to 'unstable' or 'experimental' or migrated to 'bullseye', or security updates to 'buster' or 'stretch'),
 ** new versions of existing packages, which were already tested - these are always scheduled, no matter how full the queue is
 ** old versions, already tested (at least two weeks ago)
 ** and also some old versions which failed to build (at least ten days ago), if no bug has been filed.



View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/12a2449e7f971ff3db36314e755dae2b5a3b8633

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/12a2449e7f971ff3db36314e755dae2b5a3b8633
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/qa-jenkins-scm/attachments/20210429/1f23df3c/attachment.htm>