[Qa-jenkins-scm] [Git][qa/jenkins.debian.net][master] README: reproducible Debian: Update number of armhf jobs/machines.

[Vagrant Cascadian (@vagrant)]

Vagrant Cascadian pushed to branch master at Debian QA / jenkins.debian.net


Commits:
bbf5e229 by Vagrant Cascadian at 2021-06-25T18:19:21-07:00
README: reproducible Debian: Update number of armhf jobs/machines.

- - - - -


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, 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 36 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 45 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`
 
@@ -127,10 +127,11 @@ Installation tests inside chroot environments.
 ** for 'i386' we are also using four virtual machines, ionos(2+6+12+16)-i386, which have 10 or 9 cores and 36gb ram each. ionos2+12 run emulated AMD Opteron CPUs and ionos6+16 Intel Xeon CPUs. These nodes are also sponsored by link:https://jenkins.debian.net/userContent/thanks.html[IONOS].
 ** for 'arm64' we are using eight "moonshot" sleds, codethink9-15-arm64, which have 8 cores and 64gb ram each. These nodes are sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Codethink].
 ** To test 'armhf' we are using 13 small boards hosted by vagrant at reproducible-builds.org:
+*** two quad-cores (cbxi4pro0, wbq0) with 2gb ram,
 *** six quad-cores (cbxi4a, cbxi4b, ff4a, jtx1a, jtx1b, jtx1c) with 4gb ram,
 *** one hexa-core (ff64a) with 4gb ram,
-*** two quad-core (virt32a, virt64a) with 15gb ram,
 *** four quad-core (virt32b, virt32c, virt64b, virt64c) with 7gb ram,
+*** two quad-core (virt32a, virt64a) with 15gb ram,
 * 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:



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

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/bbf5e229348868b983e3c97e15b7e9a3c6d0f41b
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/20210626/e21aa014/attachment-0001.htm>