diff options
| -rw-r--r-- | TODO | 56 |
1 files changed, 4 insertions, 52 deletions
@@ -23,13 +23,10 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian ** create d-i_svn_trigger job to trigger sub-set jobs (like manual) ** create d-i git hooks * get rid of some reduncacy in job-cfg/*.yaml -** this seems to be helpful: http://en.wikipedia.org/wiki/YAML#References (pyyaml which jenkins-job-builder uses supports them) -** FIXME: sometimes true and some True used in yaml files * fully automate backup and backup /var/lib/jenkins/jobs /var/lib/munin /var/log /root/ too * try awstats * put kgb-client.conf in git and sed passwords from filesystem into it... * push jenkins munin plugins upstream -* rgrep for ftp.de and put this into a config file. and then put other stuff in that config file, like webserver for d-i preseeding. etc. * some way to map failing jobs to debian bugs and display that in the job.... (probably via a 2nd build step) == Debian Packaging related @@ -37,10 +34,12 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian * /usr/sbin/jenkins.debian.net-setup needs to be written * what update-j.d.n.sh does, needs to be put elsewhere... * debian/copyright is incorrect about some licenses: a.) the profitbricks+debian+jenkins logos b.) the preseeding files -* switch to scm trigger instead of scm pulling before releasing this as 0.1... +* better switch to scm trigger instead of scm pulling before releasing this as 0.1... === jenkins-job-builder related +* this seems to be helpful: http://en.wikipedia.org/wiki/YAML#References (pyyaml which jenkins-job-builder uses supports them) +* FIXME: sometimes true and some True used in yaml files * support for gitweb in jobs ** needs clean merge of my patches to jenkins-job-builder first... * cleanup my patches (eg add documentation) and send pull requests on github: @@ -83,7 +82,7 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian === webchecks* -* inform debian-www@ +* inform debian-www@ ? === g-i-installation_*: @@ -94,11 +93,9 @@ See link:https://jenkins.debian.net/userContent/about.html["about jenkins.debian general -* test kfreebsd * test moar images: debian wheezy+sid cd and dvd images too and use lxde cd for installing lxde + etc * use jigdo to download images - but no edu jigdo images. * still havent got http://www.os-autoinst.org/ out of my mind -* new job type: build complete image on every commit and test it with g-i === Test Debian live @@ -129,51 +126,6 @@ general Help explaining how to test tasks (ie all the language tasks) very much welcome! -=== Tests using autopkgtest - -* see https://wiki.ubuntu.com/AutomatedTesting and http://developer.ubuntu.com/packaging/html/auto-pkg-test.html -* 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 ----- - === Test co-installability ---- |