[Qa-jenkins-scm] [Git][qa/jenkins.debian.net][master] reproducible Debian: Incorporate new armhf build nodes.
Vagrant Cascadian
gitlab at salsa.debian.org
Sat May 1 07:03:28 BST 2021
Vagrant Cascadian pushed to branch master at Debian QA / jenkins.debian.net
Commits:
e5d4fff4 by Vagrant Cascadian at 2021-04-30T23:01:36-07:00
reproducible Debian: Incorporate new armhf build nodes.
Bump number of jobs for some nodes with 7GB+ of ram.
- - - - -
2 changed files:
- README
- bin/reproducible_build_service.sh
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 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 63 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`
=====================================
bin/reproducible_build_service.sh
=====================================
@@ -121,9 +121,9 @@ choose_nodes() {
arm64_31) NODE1=codethink16-arm64 NODE2=codethink13-arm64 ;;
arm64_32) NODE1=codethink16-arm64 NODE2=codethink15-arm64 ;;
# to choose new armhf jobs:
- # for i in cb3a bbx15 cbxi4pro0 ff2a ff2b ff64a jtk1a jtk1b odxu4a odxu4b odu3a opi2a opi2c p64b p64c wbq0 cbxi4a cbxi4b ff4a jtx1a jtx1b jtx1c virt32a virt32b virt64a virt64b; do echo "$i: " ; grep NODE1 bin/reproducible_build_service.sh|grep armhf|grep $i-armhf ; done
- # 6 jobs for quad-cores with 15 gb ram
- # 6 jobs for quad-cores with 7 gb ram
+ # for i in cb3a bbx15 cbxi4pro0 ff2a ff2b ff64a jtk1a jtk1b odxu4a odxu4b odu3a opi2a opi2c p64b p64c wbq0 cbxi4a cbxi4b ff4a jtx1a jtx1b jtx1c virt32a virt32b virt32c virt64a virt64b virt64c; do echo "$i: " ; grep NODE1 bin/reproducible_build_service.sh|grep armhf|grep $i-armhf ; done
+ # 6-8 jobs for quad-cores with 15 gb ram
+ # 6-7 jobs for quad-cores with 7 gb ram
# 6 jobs for quad-cores with 4 gb ram
# 4 jobs for octo-cores with 2 gb ram
# 4 jobs for hexa-cores with 2 gb ram
@@ -133,12 +133,12 @@ choose_nodes() {
# Don't forget to update README with the number of builders…!
#
armhf_1) NODE1=bbx15-armhf-rb NODE2=jtx1a-armhf-rb ;;
- armhf_2) NODE1=bbx15-armhf-rb NODE2=ff4a-armhf-rb ;; # 32-bit lpae
+ armhf_2) NODE1=bbx15-armhf-rb NODE2=virt64c-armhf-rb ;;
armhf_3) NODE1=cb3a-armhf-rb NODE2=jtx1a-armhf-rb ;;
armhf_4) NODE1=cb3a-armhf-rb NODE2=jtx1c-armhf-rb ;;
armhf_5) NODE1=cbxi4a-armhf-rb NODE2=p64c-armhf-rb ;;
armhf_6) NODE1=jtx1a-armhf-rb NODE2=ff4a-armhf-rb ;;
- armhf_7) NODE1=ff4a-armhf-rb NODE2=cbxi4b-armhf-rb ;; # 32-bit
+ armhf_7) NODE1=virt64a-armhf-rb NODE2=cbxi4b-armhf-rb ;;
armhf_8) NODE1=p64b-armhf-rb NODE2=virt32b-armhf-rb ;;
armhf_9) NODE1=virt64b-armhf-rb NODE2=cbxi4a-armhf-rb ;;
armhf_10) NODE1=virt64a-armhf-rb NODE2=ff4a-armhf-rb ;;
@@ -167,14 +167,14 @@ choose_nodes() {
armhf_35) NODE1=p64b-armhf-rb NODE2=ff2a-armhf-rb ;;
armhf_36) NODE1=p64c-armhf-rb NODE2=ff2b-armhf-rb ;;
armhf_38) NODE1=wbq0-armhf-rb NODE2=ff2b-armhf-rb ;; # 32-bit
- armhf_39) NODE1=wbq0-armhf-rb NODE2=cbxi4a-armhf-rb ;; # 32-bit armmp
+ armhf_39) NODE1=virt64c-armhf-rb NODE2=cbxi4a-armhf-rb ;;
armhf_40) NODE1=cbxi4a-armhf-rb NODE2=jtx1b-armhf-rb ;;
armhf_41) NODE1=cbxi4a-armhf-rb NODE2=cb3a-armhf-rb ;; # 32-bit
armhf_42) NODE1=cbxi4b-armhf-rb NODE2=bbx15-armhf-rb ;; # 32-bit
armhf_43) NODE1=cbxi4b-armhf-rb NODE2=cb3a-armhf-rb ;; # 32-bit
armhf_44) NODE1=cbxi4b-armhf-rb NODE2=ff64a-armhf-rb ;;
- armhf_45) NODE1=ff4a-armhf-rb NODE2=jtk1a-armhf-rb ;; # 32-bit lpae
- armhf_46) NODE1=ff4a-armhf-rb NODE2=jtx1c-armhf-rb ;;
+ armhf_45) NODE1=ff4a-armhf-rb NODE2=virt64b-armhf-rb ;;
+ armhf_46) NODE1=virt32c-armhf-rb NODE2=jtx1c-armhf-rb ;;
armhf_47) NODE1=jtx1a-armhf-rb NODE2=cbxi4b-armhf-rb ;;
armhf_48) NODE1=jtx1a-armhf-rb NODE2=virt32a-armhf-rb ;;
armhf_49) NODE1=jtx1b-armhf-rb NODE2=bbx15-armhf-rb ;;
@@ -184,9 +184,17 @@ choose_nodes() {
armhf_53) NODE1=jtk1a-armhf-rb NODE2=wbq0-armhf-rb ;; # 32-bit
armhf_54) NODE1=jtk1a-armhf-rb NODE2=ff64a-armhf-rb ;;
armhf_55) NODE1=virt32a-armhf-rb NODE2=virt64a-armhf-rb ;;
- armhf_56) NODE1=ff64a-armhf-rb NODE2=jtk1b-armhf-rb ;;
+ armhf_56) NODE1=ff64a-armhf-rb NODE2=virt32c-armhf-rb ;;
armhf_57) NODE1=p64c-armhf-rb NODE2=opi2a-armhf-rb ;;
armhf_58) NODE1=odu3a-armhf-rb NODE2=p64b-armhf-rb ;;
+ armhf_59) NODE1=virt64c-armhf-rb NODE2=ff4a-armhf-rb ;;
+ armhf_60) NODE1=virt64c-armhf-rb NODE2=virt32c-armhf-rb ;;
+ armhf_61) NODE1=wbq0-armhf-rb NODE2=virt64c-armhf-rb ;;
+ armhf_62) NODE1=ff4a-armhf-rb NODE2=virt64c-armhf-rb ;;
+ armhf_63) NODE1=virt32c-armhf-rb NODE2=virt64a-armhf-rb ;;
+ armhf_64) NODE1=virt64c-armhf-rb NODE2=jtk1a-armhf-rb ;;
+ armhf_65) NODE1=virt32c-armhf-rb NODE2=jtk1b-armhf-rb ;; # 32-bit lpae
+ armhf_66) NODE1=ff4a-armhf-rb NODE2=virt32c-armhf-rb ;; # 32-bit lpae
*) NODE1=undefined
;;
esac
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/e5d4fff4b67e738e99fc3fdc5fb12a25205275ab
--
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/e5d4fff4b67e738e99fc3fdc5fb12a25205275ab
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/20210501/ef827967/attachment-0001.htm>
More information about the Qa-jenkins-scm
mailing list