1. About jenkins.debian.net

https://jenkins.debian.net is a tool for automated quality monitoring of Debian. It is work in progress despite being in existence since October 15th 2012.

Get the source by running git clone git://git.debian.org/git/qa/jenkins.debian.net.git. It’s all in there, no (relevant) manual setup has been done besides what’s in this git repository. (The irrelevant bits are some very simple configuration files containing passwords.)

The (virtualized) hardware is sponsored since October 2012 by http://www.profitbricks.com - currently it’s using 15 cores and 50 GB memory, thanks a lot!

Some stats are available using munin-plugins for jenkins.

If you notice some jobs has problems and you want to find out why, read debug certain jobs to learn how to do this locally.

2. Notifications

There are two types of notifications being used: email and IRC. At the end of each builds console log it says to where notifcations has been send. An adress of the form jenkins-foo means an IRC notification has been send to the #foo IRC channel.

3. Jobs being run

There are over 400 jobs being run currently. If you can think of ways to improve the usefulness of certain jobs, please do give feedback!

3.1. g-i-installation jobs

Installation tests with g-i, the graphical version of d-i, the debian-installer.

  • g-i-installation_debian_sid_daily-rescue

    • boot of rescue system with daily build sid image

  • g-i-installation_debian_sid_daily-lxde and -xfce and -kfreebsd and -hurd

    • sid installation of Xfce/LXDE desktop with daily build sid image

  • g-i-installation_debian_jessie_lxde,-xfce,-kde and -gnome and -kfreebsd

    • jessie installation of Xfce/LXDE/KDE desktop and kfreebsd install with weekly build jessie image

  • g-i-installation_debian_wheezy_lxde,-xfce,-kde and -gnome and -kfreebsd

    • wheezy installation of Xfce/LXDE/KDE desktop and kfreebsd install with wheezy release image

3.2. debian-installer jobs

  • d_i_build_$source_package

    • there is one job for each git repo referred to in http://anonscm.debian.org/viewvc/d-i/trunk/.mrconfig?view=co

    • each job pdebuilds the master branch of its git repo on every git push in a sid environment. (If the architecture(s) specified in debian/control are not amd64,all or any the build exits cleanly.)

    • while these jobs are triggered on commits, the SCM is only polled every 6min to see if there are new commits.

  • d_i_manual

    • builds the full installation-guide package with pdebuild in sid on every commit to svn://anonscm.debian.org/svn/d-i/ matching suitable patterns.

    • while this job is triggered on commits, the SCM is only polled every 15min to see if there are new commits.

  • d_i_manual_$language_html

    • builds a language (on wheezy) on every commit of svn/trunk/manual/$LANG with make languages=$LANG architectures=amd64 formats=html.

    • while these jobs are triggered on commits, the SCM is only polled every 15min to see if there are new commits.

    • on successful build, d_i_manual_$lang_pdf is triggered.

  • d_i_parse_build_logs - parses logs from http://d-i.debian.org/daily-images/build-logs.html daily, to give them a bit more exposure.

    • this job is run daily.

3.3. chroot-installation jobs

Installation tests inside chroot environments.

  • chroot-installation_maintainance_$distro:

    • make sure chroots have been cleaned up properly

    • runs daily at 05:00 UTC and triggers the $distro specific bootstrap job on success

    • wheezy is only triggered on the 4th day and 18th of each month (as it was released on the 4th)

    • squeeze only on the 25th of each month

  • $distro-bootstrap jobs:

    • just debootstrap $distro (install a base Debian distribution $distro)

    • there is one job for sid, one for wheezy and one for jessie: chroot-installation_sid_bootstrap, chroot-installation_wheezy_bootstrap and chroot-installation_jessie_bootstrap

  • plus there is chroot-installation_squeeze_bootstrap_upgrade_to_wheezy, which bootstraps squeeze and upgrades that to wheezy

    • on successful run of the bootstrap job, six $distro-install(+upgrade) jobs are triggered.

  • FIXME: describe upgrade jobs here too

  • $distro-install jobs (and $distro-install+upgrade jobs):

    • debootstrap $distro, install a $set_of_packages (and upgrade to $2nd_distro)

    • these $set_of_packages exist: gnome, kde, kde-full, lxde, xfc, full_desktop (all five desktops plus vlc evince iceweasel chromium cups build-essential devscripts wine texlive-full asciidoc vim emacs and (libreoffice virt-manager mplayer2 (jessie/sid) or openoffice virtualbox mplayer (squeeze/wheezy)) and develop

      • install is done with apt-get install, except for develop where apt-get build-dep is used to install the build dependencies of these packages.

  • All Debian Edu related jobs can be seen at these two URLs:

  • Then there are three types of jobs:

    • g-i-installation_$(distro)_$(profile):

      • tests installation of a profile with preseeding in the graphical installer,

      • screenshots and logs are preserved and a movie created,

      • testing clients against the main-server is planned too, for some time…

    • chroot-installation_$(distro)install$(education-metapackage):

      • tests apt installation of a metapackage in a specic distro.

  • edu-packages_$(distro)_$(src-package):

    • builds one of the six debian-edu packages (debian-edu, debian-edu-config, debian-edu-install, debian-edu-doc, debian-edu-artwork, debian-edu-archive-keyring on every push to it’s git master branch

    • and whenever debian-edu-doc is build, https://jenkins.debian.net/userContent/debian-edu-doc/ get’s updated automatically afterwards too.

  • Currently there are two types, one for lintian and one for piuparts.

  • The both simply build the master branch of the lintian GIT repository on every commit against sid. If that succeeds, the same source will be build on jessie and then on wheezy. (piuparts will not be build on wheezy as its current build depends do not exists in wheezy.)

3.6. haskell jobs

3.7. rebootstrap jobs

3.8. reproducible jobs

  • See https://wiki.debian.org/ReproducibleBuilds to learn more about "Reproducible Builds" in Debian and beyond.

  • Several jobs are being used to test whether packages be build reproducible or not. The result is the website https://reproducible.debian.net which is actually just a collection of html files being served from this host.

  • There are three builder jobs, alpha+beta+gamma which are each started every 2min.. There is a scheduler jobs scheduling builds for them, and job to setup and update the pbuilder base.tgz archives for the different suites.

  • Several other jobs exist to build the html pages, to create a JSON file which can be downloaded from https://reproducible.debian.net/reproducible.json.

  • The SQLite database used can be downloaded from https://reproducible.debian.net/reproducible.db.

  • The reproducible build jobs use their own pbuilder base.tgz, which has the reproducible apt repo added. And there another sid schroot is being used, where debbindiff (which has lots of depends installed) is run from.

  • Manual rescheduling of packages is easy, if you have console access. (Hint: you don’t but someone on #debian-reproducible will have.) This is how to:

jenkins@jenkins:~$ /srv/jenkins/bin/reproducible_schedule_on_demand.sh package1 package2 abcde
  • blacklisting packages can be done similarily, optionally list reaons in notes.git/packages.yml

jenkins@jenkins:~$ /srv/jenkins/bin/reproducible_blacklist.sh package1

3.9. dvswitch jobs

  • There are three jobs currently:

    • dvswitch_sid and dvswitch_jessie build the master branch of dvswitch against that environment.

    • while dvswitch_against_libav_git builds the master branch of dvswitch using libav also build from it’s master branch. This is done in an sid environment.

    • Except for dvswitch_jessie which is triggered by a successful dvswitch_sid run, the jobs are triggered by git commits.

3.10. jenkins.d.n jobs

These are jobs for making sure jenkins.debian.net is running smoothly.

4. Debugging certain jobs

FIXME: To debug certain jobs, a jenkins setup is actually not needed. Make this easy and describe here.

This is work in progress too, but mostly just needs documentation! In principle the shell commands from the various jobs should run on any Debian system just fine. Please use a test system though, as all your data might be eaten.

  • Build this source as a debian package and install the jenkins.d.n-debug package and all it’s recommends.

4.1. Feedback

I love to get feedback on this! Either by sending an email to debian-qa@lists.debian.org or by joining #debian-qa on irc.debian.org and expressing yourself there. The best way is to qa.debian.org@packages.debian.org">report bugs, even better if accompanied by patches or pull requests. But really, all feedback is appreciated!

4.2. Setup


4.3. ToDo

There is still a lot of work left, check the current ToDo list.

4.4. Thanks


5. License

  • everything except features and bin/libvirt_cucumber_tests:

  • features and bin/libvirt_cucumber_tests:

    • GPLv3+