diff options
-rw-r--r-- | TODO | 46 |
1 files changed, 23 insertions, 23 deletions
@@ -17,23 +17,14 @@ About jenkins.debian.net * (virtual) hardware sponsored by http://www.profitbricks.com - currently it's just a server, but in future there will be installation and tests clients started on demand as well. * some stats are available at http://jenkins.debian.net/munin/jenkins-month.html -== General ToDo +== More tests to be run -* get rid of reduncacy in job-cfg/*.yaml and also fix the FIXMEs there -* add documentation for jenkins-job-builder: -** publisher:logparse -** svn:scm -* mail notifications (to where?) -* proper backup (=daily), see bottom of this document for what to backup -* make job configuration visible to un-authenticated users -* squid has problems with SO_FAIL -* split TODO and about.txt? -** use debian stylesheet for about.html -** add sidebar links for all jobs -* proper git repo url, outside users/holger -* only trigger (=really run) jobs if available+used packages have changed (save packages in db and compare) +=== Tests for supporting d-i development: -== More tests to be run +* build the manual on every svn commit +** later: notify debian-boot@l.d.o and #debian-boot +* run scripts/digress/ +* bubulle wrote: "Another interesting target would be d-i builds *including non uploaded packages* (something like "d-i from git repositories" images). That would in some way require to create a quite specific image, with all udebs (while netboot only has udebs needed before one gets a working network setup). === Test cd-images: @@ -45,7 +36,7 @@ About jenkins.debian.net === Test tasks: -* test installation with (at least) more language tasks enabled +* test installations with (at least) more language tasks enabled ---- <h01ger> how do i install a task outside d-i? @@ -56,13 +47,6 @@ About jenkins.debian.net (FIXME: tasksel doesn't work like this) -=== Tests for supporting d-i development: - -* build the manual on every svn commit -** later: notify debian-boot@l.d.o and #debian-boot -* run scripts/digress/ -* bubulle wrote: "Another interesting target would be d-i builds *including non uploaded packages* (something like "d-i from git repositories" images). That would in some way require to create a quite specific image, with all udebs (while netboot only has udebs needed before one gets a working network setup). - === Tests using autopkgtest * I aware but also lost, after looking at /usr/share/doc/autopkgtest/ - wanna help? @@ -71,6 +55,22 @@ About jenkins.debian.net ** this only lists a few packages, so a very first test could be to compare this list against this: `wget -q http://http.debian.net/debian/dists/unstable/main/Contents-source.gz -O- | zgrep -m1 -E '^debian/tests/control\s'`, make a job out of it and make it UNSTABLE if the diff is non-zero. And as a second step, run those tests... * also see http://dep.debian.net/deps/dep8/ +== General ToDo + +* get rid of some reduncacy in job-cfg/*.yaml and also fix the FIXMEs there +* add documentation for jenkins-job-builder: +** publisher:logparse +** svn:scm +* mail notifications (to where?) +* proper backup (=daily), see bottom of this document for what to backup +* make job configuration visible to un-authenticated users +* squid has problems with SO_FAIL +* split TODO and about.txt? +** use debian stylesheet for about.html +** add sidebar links for all jobs +* proper git repo url, outside users/holger +* only trigger (=really run) jobs if available+used packages have changed (save packages in db and compare) + == Installed software that makes jenkins.debian.net run * jenkins.debian.net runs Debian wheezy. |