[Qa-jenkins-scm] [Git][qa/jenkins.debian.net][master] TODO: cleanup

Holger Levsen (@holger) gitlab at salsa.debian.org
Thu Jul 14 12:42:23 BST 2022



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


Commits:
f5a2e7aa by Holger Levsen at 2022-07-14T13:42:16+02:00
TODO: cleanup

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

- - - - -


1 changed file:

- TODO


Changes:

=====================================
TODO
=====================================
@@ -24,13 +24,11 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian
 ** EXECUTOR_NUMBER for X
 * run all bash scripts with set -u and set -o pipefail: http://redsymbol.net/articles/unofficial-bash-strict-mode/
 * teach bin/chroot-*.sh and bin/d-i_build.sh how to nicely deal with network problems… (as both reproducible_build.sh and schroot-create.sh do)
-* this is outdated with salsa: add to all git post-receive hooks: `curl -s "https://jenkins.debian.net/git/notifyCommit?url=https://salsa.debian.org/installer-team/$(basename $PWD .git)"` which will trigger jenkins to pull (check) that git repo…
 * salsa stuff:
 ** triggers for d-i repos are missing
 
 === nodes at OSUOSL
 
-* add to README 
 * add link to OSUOSL in THANKS and explain usage
 * blog post when done
 * setup netconsoles:
@@ -51,7 +49,7 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian
 
 === Debian rebuilder 'thing'
 
-(these notes are probably mostly obsolete now.)
+(these notes are mostly obsolete now.)
 
 * prototype only dealing with bullseye and amd64 (and arch all packages)
 ** 1st step: download a specific .buildinfo file and sbuild it - done
@@ -107,7 +105,6 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian
 
 === jenkins-job-builder related
 
-* investigate whether its possible nowadays to let it delete jobs which were removed.. nope. But there is a Makefile now which will find zombies…
 * yaml could be refactored, lots of duplication in there. this seems to be helpful: http://en.wikipedia.org/wiki/YAML#References (pyyaml which jenkins-job-builder uses supports them)
 
 === debugging job runs should be made easy
@@ -215,17 +212,6 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian
 * see https://wiki.debian.org/ReproducibleInstalls
 * run this as a new job
 
-==== reproducible non-Debian tests, new host for 398 day variation is unused
-
-* locations in the code which need to be changed
-** RPM_BUILD_NODE=osuosl171-amd64
-** grep for osuosl171-amd64, there's more
-* IOW: these tests should use it:
-** coreboot
-** netbsd
-** fedora
-** (fdroid)
-
 ==== reproducible coreboot
 
 * add more variations: domain+hostname, uid+gid, USER, UTS namespace
@@ -481,6 +467,7 @@ correctly, Guix is ready for work.
 
 == Debian Packaging related
 
-This setup should come as a Debian source package...
+This setup should ideally come as a Debian source package, one far away day maybe.
+
 
 // vim: set filetype=asciidoc:



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

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/f5a2e7aad4b19fc5b3b461b6288e3fb10780a908
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/20220714/93c51011/attachment-0001.htm>


More information about the Qa-jenkins-scm mailing list