update documentation and todo

1 files changed, 64 insertions, 12 deletions

diff --git a/TODO b/TODO
index 243ace15..87b14bb9 100644
--- a/TODO
+++ b/TODO
@@ -14,11 +14,25 @@ See link:http://jenkins.debian.net/userContent/about.html["about jenkins.debian.
 
 == General ToDo
 
+* switch git:// and svn:// urls to http:// and thus use proxy. increase polling frequency to 2min.
 * general housekeeping job:
 ** run calamaris, visitors etc
 ** check for stale processes
 ** check for apt-upgrades
 ** check for jobs forgetting their triggers
+* proper git repo url, outside users/holger
+** same for /srv/jenkins.debian.net-scm-sync.git
+* chroot-tests: only trigger (=really run) jobs if available+used packages have changed (save packages in db and compare)
+* update jdk
+* fully automate backup and full backup /var/lib/jenkins/jobs and /var/lib/munin and /var/log too
+* try awstats
+
+=== Bugs
+
+* html_publisher doesn't make the results of d-i_manual_* available
+
+=== jenkins-job-builder related
+
 * support for gitweb in jobs 
 ** needs clean merge of my patches to jenkins-job-builder first...
 * get rid of some reduncacy in job-cfg/*.yaml 
@@ -28,28 +42,28 @@ See link:http://jenkins.debian.net/userContent/about.html["about jenkins.debian.
 ** svn:scm
 ** properties: sidebar
 * file a bug about jenkins/jenkins-job-builder sometimes "forgetting" about triggers
-* mail notifications (to where?)
-* proper git repo url, outside users/holger
-** same for /srv/jenkins.debian.net-scm-sync.git
-* only trigger (=really run) jobs if available+used packages have changed (save packages in db and compare)
-* update jdk
-* fully automate backup and full backup /var/lib/jenkins/jobs and /var/lib/munin and /var/log too
-* try awstats
 
 == More tests to be run
 
 === d-i_manual*
 
-* html_publisher doesn't make the results of d-i_manual_* available
-* svn:trunk:packages/po/* triggers nothing
-* notify #debian-boot about jenkins jobs results
+* svn:trunk/manual/po triggers the full build, should trigger language specific builds.
+----
+As documented in manual/doc/translations_po.txt:
+        Use the following commands:
+          1. ./scripts/merge_xml en
+          2. ./scripts/update_pot
+          3. ./scripts/update_po <your language>
+          4. ./scripts/revert_pot
+          5. ./scripts/create_xml <your language>
+----
+* inform translators (and debian-boot for the package)
 
 === d-i_build*
 
 * 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).
-* notify #debian-boot about jenkins jobs results
-* run scripts/digress/
+* inform debian-boot@ ?
 
 === chroot-test_*
 
@@ -89,3 +103,41 @@ Help explaining how to test tasks (ie all the language tasks) very much welcome!
 * finding packages with autopkgtests: http://lists.debian.org/debian-qa/2012/11/msg00012.html
 ** 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/
+* also from that thread on debian-qa@l.d.o:
+----
+Subject: Re: automated tests or builds for d-i
+From: Martin Pitt <mpitt@debian.org>
+
+  Stefano Zacchiroli [2012-11-04 14:51 +0100]:
+> AFAIK in Ubuntu they've glue code that hooks autopkgtest tests into
+> jenkins. I don't know where the code is or how Ubuntu-specific it is,
+> but it is worth investigating. It'd be awesome to make it as
+> distro-agnostic as possible, enabling all derivatives to run their own
+> autopkgtest tests: it'd be a nice way to spot regressions introduced by
+> distro-specific patches and more.
+
+Indeed, our goal is to get a lot more of them. We currently have some
+20 [1], but at the last UDS we had a little competition which got us
+another 11 [2], which we'll upload and forward to Debian in the next
+days.
+
+Our scripts for creating VMs, running the tests in those, and the
+Jenkins integration are in "bzr branch lp:auto-package-testing", which
+you can browse at [3]. In the doc/ directory there is documentation
+how the Jenkins integration works. I can't say much about it I'm
+afraid, as I have never touched a Jenkins job so far; this has been
+created by Jean-Baptiste Lallement (in CC:); he's on holiday for the
+next week, though.
+
+Please let me know if this is useful. I can poke at the jobs in our
+actual Jenkins instance (jenkins.qa.u.c. is just a readonly public
+mirror) if you need to know something specific, but we try to avoid
+having any manual job configuration; these are all autogenerated
+through scripts through python-jenkins.
+
+Martin
+
+[1] https://jenkins.qa.ubuntu.com/view/Quantal/view/AutoPkg%20Test/
+[2] https://bugs.launchpad.net/ubuntu/+bugs?field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.tag=udstestcompetition
+[3] http://bazaar.launchpad.net/~auto-package-testing-dev/auto-package-testing/trunk
+----