[Git][qa/jenkins.debian.net][master] 2 commits: clarify what to do when once forky has been released

Holger Levsen (@holger) gitlab at salsa.debian.org
Thu Aug 14 15:30:35 BST 2025



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


Commits:
3b7fa195 by Holger Levsen at 2025-08-14T16:30:02+02:00
clarify what to do when  once forky has been released

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

- - - - -
208e1ed5 by Holger Levsen at 2025-08-14T16:30:27+02:00
trbod: retain abilitiy to do graphs for i386

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

- - - - -


3 changed files:

- TODO.forky
- TODO.trixie
- bin/reproducible_common.sh


Changes:

=====================================
TODO.forky
=====================================
@@ -6,15 +6,9 @@ this is the stuff which needs to be done when forky has been released.
 * in general: keep jenkins running under trixie until we test duke everywhere. *then* upgrade jenkins.
 * the other nodes can be upgraded whenever.
 
-=== Things to be done for tests.r-b.o:
+=== Things to be done for tests.r-b.o to test duke:
 
-* confirm postgres19 cluster is working on ionos7
-** then drop postgres17 cluster on i7: pg_dropcluster 17 main
-* confirm postgres19 cluster is working on jenkins
-** backup new cluster
-** then drop postgres17 cluster on jenkins: pg_dropcluster 17 main
-
-* tests.r-b.o/debian:
+* upgrade tests.r-b.o/debian to test duke (and drop bookworm)
 ** pause building: 
 *** sudo touch /var/lib/jenkins/NO-RB-BUILDERS-PLEASE
 *** sudo systemctl --user -M jenkins@ stop 'reproducible_build@*.service'
@@ -46,9 +40,24 @@ this is the stuff which needs to be done when forky has been released.
 ** update find_obsolete_transitional_packages.sh and job-cfg/obsolete-transitional.yaml
 ** update suite names in README
 
-=== Things to be done for r.d.n:
+=== Things to be done for r.d.n to test duke:
 
 * unclear/out of scope for this document so far
 
+=== Things to be done for all systems to run forky
+
+* upgrade all the systems to forky
+** start with all the boring and easy ones, that means:
+*** leave out jenkins, ionos7 and osuosl5.
+** once the boring ones are done:
+*** upgrade ionos7
+**** confirm postgres19 cluster is working on ionos7
+**** then drop postgres17 cluster on i7: pg_dropcluster 17 main
+*** upgrade osuosl5
+*** upgrade jenkins
+**** confirm postgres19 cluster is working on jenkins
+**** backup new cluster
+**** then drop postgres17 cluster on jenkins: pg_dropcluster 17 main
+
 
 // vim: set filetype=asciidoc:


=====================================
TODO.trixie
=====================================
@@ -3,7 +3,5 @@
 
 * on jenkins and ionos7 once we are sure they run fine: pg_dropcluster 15 main
 * breakage job broken
-* missing armhf history page: https://tests.reproducible-builds.org/debian/buster/index_suite_armhf_stats.html
-* will probably tomorrow be there: https://tests.reproducible-builds.org/debian/forky/amd64/index_pkg_sets.html
 
 // vim: set filetype=asciidoc:


=====================================
bin/reproducible_common.sh
=====================================
@@ -823,6 +823,9 @@ create_debian_png_from_table() {
 	if [ "$ARCH" = "armhf" ] ; then
 		# armhf was only build since 2015-08-30
 		WHERE2_EXTRA="WHERE s.datum >= '2015-08-30'"
+	elif [ "$ARCH" = "i386" ] ; then
+		# i386 was only build since 2016-03-28
+		WHERE2_EXTRA="WHERE s.datum >= '2016-03-28'"
 	elif [ "$ARCH" = "arm64" ] ; then
 		# arm63 was only build since 2016-12-23
 		WHERE2_EXTRA="WHERE s.datum >= '2016-12-23'"
@@ -841,6 +844,11 @@ create_debian_png_from_table() {
 				# unstable/armhf was only build since 2015-08-30 (and experimental/armhf since 2015-12-19 and stretch/armhf since 2016-01-01)
 				WHERE_EXTRA="$WHERE_EXTRA AND datum >= '2015-08-30'"
 			fi
+		elif [ "$ARCH" = "i386" ]  ; then
+			if [ $1 -eq 2 ] ; then
+				# i386 was only build since 2016-03-28
+				WHERE_EXTRA="$WHERE_EXTRA AND datum >= '2016-03-28'"
+			fi
 		elif [ "$ARCH" = "arm64" ]  ; then
 			if [ $1 -eq 2 ] ; then
 				# arm64 was only build since 2016-12-23



View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/compare/f3496be2ddd45d2dfbd5751daae6ee54a09711ab...208e1ed51c350182f426c1bd87b98b18c4156c5d

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/compare/f3496be2ddd45d2dfbd5751daae6ee54a09711ab...208e1ed51c350182f426c1bd87b98b18c4156c5d
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/20250814/a6aa0a1f/attachment-0001.htm>


More information about the Qa-jenkins-scm mailing list