[Git][qa/jenkins.debian.net][master] t.r-b.o/d: continue WIP, almost there
Holger Levsen (@holger)
gitlab at salsa.debian.org
Wed Aug 13 16:10:42 BST 2025
Holger Levsen pushed to branch master at Debian QA / jenkins.debian.net
Commits:
3e23fa7d by Holger Levsen at 2025-08-13T17:10:34+02:00
t.r-b.o/d: continue WIP, almost there
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
5 changed files:
- README
- TODO.trixie
- job-cfg/obsolete-transitional.yaml
- job-cfg/packages-tests.yaml
- job-cfg/piuparts.yaml
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, six suites, 'buster', 'bullseye', 'bookworm', 'trixie', 'unstable' and 'experimental', are tested on three architectures: 'amd64', 'arm64' and 'armhf'. The tests are done using 'pbuilder' through several concurrent workers: 40 for 'amd64', 32 for 'arm64' and 35 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, four suites, 'bookworm', 'trixie', 'forky', 'unstable' and 'experimental', are tested on three architectures: 'amd64', 'arm64' and 'armhf'. The tests are done using 'pbuilder' through several concurrent workers: 40 for 'amd64', 32 for 'arm64' and 35 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 && sudo systemctl --user -M jenkins@ stop reproducible-build at .service && /srv/jenkins/bin/reproducible_cleanup_nodes.sh`
** To start all the workers use: `sudo systemctl start reproducible_build`
@@ -134,7 +134,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 'trixie', or security updates to 'bookworm', 'bullseye' or 'buster'),
+** new untested packages (either uploaded to 'unstable' or 'experimental' or migrated to 'forky', or security updates to 'trixie' or 'bookworm'),
** 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.
=====================================
TODO.trixie
=====================================
@@ -2,9 +2,6 @@
== ToDo, after we released trixie
* on jenkins and ionos7 once we are sure they run fine: pg_dropcluster 15 main
-* update find_obsolete_transitional_packages.sh and job-cfg/obsolete-transitional.yaml
-* add trixie jobs in job-cfg/packages-tests.yaml, drop buster ones
-* add trixie jobs in job-cfg/piuparts.yaml, drop buster ones
-* update suite names in README
+* anything we missed should be added to TODO.forky
// vim: set filetype=asciidoc:
=====================================
job-cfg/obsolete-transitional.yaml
=====================================
@@ -17,7 +17,7 @@
artifactDaysToKeep: -1
artifactNumToKeep: -1
builders:
- - shell: '/srv/jenkins/bin/find_obsolete_transitional_packages.sh trixie bookworm bullseye'
+ - shell: '/srv/jenkins/bin/find_obsolete_transitional_packages.sh forky trixie bookworm'
publishers:
- logparser:
parse-rules: '/srv/jenkins/logparse/obsolete-transitional.rules'
=====================================
job-cfg/packages-tests.yaml
=====================================
@@ -48,13 +48,13 @@
regular-expression: '^ERROR: Error cloning remote repo'
my_default_distro_matrix: &distros_defaults
- sid: &distro_defaults_sid
- my_trigger: '{name}_trixie'
+ my_trigger: '{name}_forky'
my_origin_triggers: &default_git_triggers
- pollscm:
cron: '15,30,45,60 * * * *'
- - trixie: &distro_defaults_trixie
- my_trigger: '{name}_bookworm'
- - bookworm: &distro_defaults_bookworm {}
+ - forky: &distro_defaults_forky
+ my_trigger: '{name}_trixie'
+ - trixie: &distro_defaults_trixie {}
- defaults:
<<: *DEFAULTS
@@ -86,8 +86,8 @@
my_description: 'debian-archive-keyring testsuite'
my_distro:
- sid: *distro_defaults_sid
- - trixie: *distro_defaults_trixie
- - bookworm: {}
+ - forky: *distro_defaults_forky
+ - trixie: {}
jobs:
- simple
@@ -99,7 +99,7 @@
my_description: 'Debian/Debsums testsuite'
my_distro:
- sid: *distro_defaults_sid
- - trixie: *distro_defaults_trixie
- - bookworm: {}
+ - forky: *distro_defaults_forky
+ - trixie: {}
jobs:
- simple
=====================================
job-cfg/piuparts.yaml
=====================================
@@ -87,11 +87,11 @@
- job-template:
defaults: piuparts-tests
- name: '{name}_testsuite_bookworm'
+ name: '{name}_testsuite_trixie'
- job-template:
defaults: piuparts-tests
- name: '{name}_testsuite_trixie'
+ name: '{name}_testsuite_forky'
- job-template:
defaults: piuparts-tests
@@ -99,11 +99,11 @@
- job-template:
defaults: piuparts-builds
- name: '{name}_build_bookworm'
+ name: '{name}_build_trixie'
- job-template:
defaults: piuparts-builds
- name: '{name}_build_trixie'
+ name: '{name}_build_forky'
- job-template:
defaults: piuparts-builds
@@ -119,30 +119,30 @@
my_origin_triggers:
- pollscm:
cron: ''
- my_trigger: 'piuparts_testsuite_trixie, piuparts_build_sid'
+ my_trigger: 'piuparts_testsuite_forky, piuparts_build_sid'
+ - '{name}_testsuite_forky':
+ my_distro: 'forky'
+ my_shell: 'make check'
+ my_description: 'run testsuite from piuparts develop branch on forky.'
+ my_trigger: 'piuparts_testsuite_trixie'
- '{name}_testsuite_trixie':
my_distro: 'trixie'
my_shell: 'make check'
my_description: 'run testsuite from piuparts develop branch on trixie.'
- my_trigger: 'piuparts_testsuite_bookworm'
- - '{name}_testsuite_bookworm':
- my_distro: 'bookworm'
- my_shell: 'make check'
- my_description: 'run testsuite from piuparts develop branch on bookworm.'
my_trigger: ''
- '{name}_build_sid':
my_distro: 'sid'
my_shell: 'debuild -uc -us'
my_description: 'build the piuparts develop branch on sid.'
+ my_trigger: 'piuparts_build_forky'
+ - '{name}_build_forky':
+ my_distro: 'forky'
+ my_shell: 'debuild -uc -us'
+ my_description: 'build the piuparts develop branch forky.'
my_trigger: 'piuparts_build_trixie'
- '{name}_build_trixie':
my_distro: 'trixie'
my_shell: 'debuild -uc -us'
- my_description: 'build the piuparts develop branch trixie.'
- my_trigger: 'piuparts_build_bookworm'
- - '{name}_build_bookworm':
- my_distro: 'bookworm'
- my_shell: 'debuild -uc -us'
- my_description: 'build the piuparts develop branch on bookworm.'
+ my_description: 'build the piuparts develop branch on trixie.'
my_trigger: ''
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/3e23fa7d2817f7ec3d68366d3b3f23c75413ee50
--
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/3e23fa7d2817f7ec3d68366d3b3f23c75413ee50
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/20250813/71e29dbf/attachment-0001.htm>
More information about the Qa-jenkins-scm
mailing list