* (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
== Jobs being run
=== chroot-tests jobs
* FIXME: describe them
=== debian-installer jobs
* FIXME: describe them
=== webcheck jobs
* FIXME: describe them
== ToDo
* There is still of work left, check the current link:http://jenkins.debian.net/userContent/todo.html[ToDo list].
== Setup
=== Installed software that makes jenkins.debian.net run
* jenkins.debian.net runs Debian wheezy.
* FIXME: describe how jenkins is installed + configured, basically put 'deb http://pkg.jenkins-ci.org/debian-stable binary/' into '/etc/apt/sources.list.d/jenkins.list' and `apt-get update`
* needed packages are listed in 'update_jdn.sh' and which will also make sure they are installed
** 'update_jdn.sh' is available in the git repo
* package configuration is kept in that git repo and deployed by 'update_jdn.sh' as well.
* (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
== More tests to be run
== General ToDo
* get rid of some reduncacy in job-cfg/*.yaml and also fix the FIXMEs there
* add documentation for jenkins-job-builder and send pull requests on github:
** publisher:logparse
** publisher:htmlpublisher
** svn:scm
** properties: sidebar
* file a bug about jenkins/jenkins-job-builder sometimes "forgetting" about triggers
* mail notifications (to where?)
* proper backup (=daily), see bottom of this document for what to backup
* proper git repo url, outside users/holger
* only trigger (=really run) jobs if available+used packages have changed (save packages in db and compare)
== More tests to be run
=== Tests for supporting d-i development:
=== Tests for supporting d-i development:
* build the manual on every commit
* notify debian-boot@l.d.o and #debian-boot about jenkins jobs results
** later: notify debian-boot@l.d.o and #debian-boot
* run scripts/digress/
* 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).
* 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).
...
@@ -55,41 +63,6 @@ About jenkins.debian.net
...
@@ -55,41 +63,6 @@ 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...
** 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 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 and send pull requests on github:
** publisher:logparse
** publisher:htmlpublisher
** svn:scm
** properties: sidebar
* mail notifications (to where?)
* proper backup (=daily), see bottom of this document for what to backup
* 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.
* FIXME: describe how jenkins is installed + configured, basically put 'deb http://pkg.jenkins-ci.org/debian-stable binary/' into '/etc/apt/sources.list.d/jenkins.list' and `apt-get update`
* needed packages are listed in 'update_jdn.sh' and which will also make sure they are installed
** 'update_jdn.sh' is available in the git repo
* package configuration is kept in that git repo and deployed by 'update_jdn.sh' as well.
cp-r TODO userContent/* /var/lib/jenkins/userContent/
cp-r TODO README userContent/* /var/lib/jenkins/userContent/
cd /var/lib/jenkins/userContent/
cd /var/lib/jenkins/userContent/
asciidoc -a numbered -a data-uri -aiconsdir=/etc/asciidoc/images/icons -ascriptsdir=/etc/asciidoc/javascripts -aimagesdir=./ -b html5 -a toc -atoclevels=4 -a icons -astylesheet=/var/lib/jenkins/userContent/theme/debian.css -o about.html TODO
ASCIIDOC_PARAMS="-a numbered -a data-uri -a iconsdir=/etc/asciidoc/images/icons -a scriptsdir=/etc/asciidoc/javascripts -a imagesdir=./ -b html5 -a toc -a toclevels=4 -a icons -a stylesheet=$(pwd)/theme/debian.css"
rm TODO
asciidoc $ASCIIDOC_PARAMS-o about.html README
explain "Updated about.html"
asciidoc $ASCIIDOC_PARAMS-o todo.html TODO
rm TODO README
explain "Updated about.html and todo.html"
#
#
# run jenkins-job-builder to update jobs if needed
# run jenkins-job-builder to update jobs if needed
