### Navigation

- index
- modules
- next
- previous
- Home »
- Contents »
- InaSAFE developer documentation »

# Continuous Integration Testing with Jenkins

Note

This documentation is Copyright Linfiniti Consulting CC. June 2012 and has been included here to provide provenance, and adapted for the InaSAFE project.

Jenkins is an automated build and test server.

Warning

These notes are a port of notes kept during setup of Jenkins for some django projects and were written after the fact. As such, they need to be proof read and validated on a new server instance.

## Installation procedure - Jenkins server

The install procedure is described at http://pkg.jenkins-ci.org/debian/.

To start, do this:

    wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -

Now add this to your `/etc/apt/sources.list`:

    deb http://pkg.jenkins-ci.org/debian binary/

Now do:

    sudo apt-get update
    sudo apt-get install jenkins

### DNS and Reverse Proxy

I set up the following subdomain http://jenkins.linfiniti.com

Now create a virtual host on the server’s apache installation to reverse proxy by creating this file: `/etc/apache2/sites-available/3-jenkins.linfiniti.com` which should contain:

    <VirtualHost *:80>
      ServerAdmin tim@linfiniti.com
      ServerName jenkins.linfiniti.com

      ProxyPass         / http://localhost:8080/
      ProxyPassReverse  / http://localhost:8080/
      ProxyRequests     Off

      # Local reverse proxy authorization override
      # Most unix distribution deny proxy by default
      # (ie /etc/apache2/mods-enabled/proxy.conf in Ubuntu)
      <Proxy http://localhost:8080/*>
        Order deny,allow
        Allow from all
      </Proxy>
      # Possible values include: debug, info, notice, warn, error, crit,
      # alert, emerg.
      LogLevel warn

      ErrorLog /var/log/apache2/jenkins.linfiniti.error.log
      CustomLog /var/log/apache2/jenkins.linfiniti.access.log combined
      ServerSignature Off

    </VirtualHost>

Now enable this vhost:

    sudo a2ensite 3-jenkins.linfiniti.com
    sudo /etc/init.d/apache reload

## Configure the server

Go to http://jenkins.linfiniti.com and log in as an admin user.

### Enable Plugins

Jenkins ‣ Manage Jenkins ‣ Manage Plugins or go to http://jenkins.linfiniti.com/pluginManager/.

Enable the following plugins:

- External Monitor Job Type Plugin
- LDAP Plugin
- pam-auth
- javadoc
- ant
- Jenkins Subversion Plug-in
- Jenkins GIT plugin
- Maven Integration plugin
- Jenkins SLOCCount Plug-in
- Jenkins Sounds plugin
- Jenkins Translation Assistance plugin
- ruby-runtime
- Jenkins CVS Plug-in
- Coverage/Complexity Scatter Plot PlugIn
- Status Monitor Plugin
- Git Parameter Plug-In
- github-api
- GitHub plugin
- Jenkins Violations plugin
- git-notes Plugin
- Twitter plugin
- Jenkins Cobertura Plugin
- Jenkins Gravatar plugin
- Jenkins SSH Slaves plugin

### Lock down access

We are hosting private repositories on the server so we want to make everything private. To do that we do: Jenkins ‣ Manage Jenkins ‣ Configure System or go to http://jenkins.linfiniti.com/configure.

Under Access control - Security Realm, check Jenkins’s own user database.

Under Authorization check Project-based Matrix Authorization Strategy, then add your admin users only here, giving them all permissions. We will add less priveledged users on a project by project basis.

### Other Configuration options

- Jenkins URL set to `http://jenkins.linfiniti.com/`
- Sender E-mail Address set to `Linfiniti Jenkins <jenkins@linfiniti.com>`
- GitHub Web Hook set to `Manually manage hook URLs`

## Creating the Jenkins Farminfo Job

Create a new Job (project):

Jenkins ‣ New Job or go to http://jenkins.linfiniti.com/view/All/newJob.

Here is a log of the options we set for the Jenkins job:

- Project Name set to `InaSAFE` (don’t use spaces for the project name!).
- Check Enable project-based security then add an entry for Anonymous with `Job: Read` and `Job Discover` permissions only. This will allow anonymous read-only access to the project.
- GitHub project set to `https://github.com/AIFDR/inasafe/`
- Source Code Management check Git and set to `git@github.com:AIFDR/inasafe.git`
- Branch Specifier (blank for default) set to `master`
- Repository browser set to `auto`
- Build Triggers set to `Build when a change is pushed to GitHub` - this will cause the project to build every time a new commit is pushed to GitHub. We also need to setup a GitHub hook to do this which is described further down.

Build Actions

- Build add an `Execute Shell` step and set the script as follows:

      export PYTHONPATH=/usr/local/qgis1.8/share/qgis/python/
      export LD_LIBRARY_PATH=/usr/local/qgis1.8/lib
      export QGIS_PREFIX_PATH=/usr/local/qgis1.8/

      # Make sure data dir is current and synced it its git clone
      scripts/update-test-data.sh

      #Go on with metrics and tests
      make jenkins-pyflakes
      make jenkins-pep8
      make jenkins-pylint
      make jenkins-sloccount
      make jenkins-test

Note

In this server instance we are using a hand built QGIS. The initial 3 export lines may not be needed if you are using a package build QGIS installation.

- Add build step set to `play a sound` and choose a sound which will play when the build completes (optional)

Post-build Actions

Add the following actions and settings:

- Publish Cobertura Coverage Report set Cobertura xml report pattern to `coverage.xml`. For the rest take the defaults or tweak them as you like.

- Publish JUnit test result report set Test report XMLs

    to `nosetests.xml`. I also disabled Retain long standard output/error (you can enable it temporarily while debugging server side build issues).

- Publish SLOCCount analysis reports set SLOCcount reports to `sloccount.sc`

- Report Violations set the following:
    - pep8 to `pep8.log`
    - pylint to `pylint.log`

- Email notification set Recipients to `tim@linfiniti.com`. Add any additional recipients as needed (space delimited). Also I set Send e-mail for every unstable build checked and Send separate e-mails to individuals who broke the build checked.

- Jenkins Sounds set Failure to `argh(wave)`

- Jenkins Sounds set Success to `Yahoo.Yodel(wave)`

- Publish Coverage / Complexity Scatter Plot check Locate the graph at the topmost of Jenkins project page

- Status Monitor enable (this is optional)

Click Save

## Server Configuration in the shell

We need to do the following on the server as the jenkins user:

### Create an ssh key for Jenkins

This key will be used to enable Jenkins access to private repos on GitHub. You only need to do this once on the server for each project:

    sudo su - jenkins
    jenkins@maps:~$ ssh-keygen
    Generating public/private rsa key pair.
    Enter file in which to save the key (/var/lib/jenkins/.ssh/id_rsa_inasafe):
    Enter passphrase (empty for no passphrase):
    Enter same passphrase again:
    Your identification has been saved in /var/lib/jenkins/.ssh/id_rsa_inasafe.
    Your public key has been saved in /var/lib/jenkins/.ssh/id_rsa_inasafe.pub.
    The key fingerprint is:
    29:7e:b6:f5:18:5e:cb:e7:f6:b7:84:e1:f5:66:31:41 jenkins@maps.linfiniti.com
    The key's randomart image is:
    +--[ RSA 2048]----+
    |               E |
    |              .  |
    |               . |
    |         .      .|
    |      . S    . + |
    |     . .    . + +|
    |      . o o .o .+|
    |       o + * .+o.|
    |        . o ++.o+|
    +++++++++++++++++++

Here’s our key:

    cat .ssh/id_rsa_inasafe.pub
    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC5f7il/lmIUQeIrcQ3f10krOOjLSwPhpJB5G6T
    LG1Dtxoyb/o/XgxPOjNfVfoVNLhB7AVp6I/IsrK3KvO8wkuOVWQ5Q5p3ntPnT6eX62JTLAlPeOGo
    MX0Iq1Vs6cOAhNK11uMfXwdUk//cht3zSlb6GLeg7mTNw/JGPAzJV4YkCcIK87H3e1ClYEU+7Kzb
    lbGKBfXWxgUPIHVRfwVZJZwbCgt1hBSBs7nJFmLqC654rRxhpFAWi72/Go79AW+YEDWUOOSZEsGc
    aT0kJ4mrks0nOMwAhcimcFqfdmmwOqIXgLPm/1jG78z08zGYhNiLOcaZDj1ULnQNmAtDx0/rCOuL
    jenkins@maps.linfiniti.com

You need to create an ssh host alias so that when doing a git checkout, the correct keypair is used. Add this to the `~/.ssh/config` of the jenkins user:

    Host InaSAFEGitHub
         IdentityFile /home/jenkins/.ssh/id_rsa_inasafe
         HostName github.com

Now go to https://github.com/AIFDR/inasafe/admin/keys and add the above key as a deploy key.

Next we add the github key to the Jenkins user’s allowed hosts. The easiest way to do this is just to make a temporary clone of the repo. Again this only needs to be done once and then Jenkins will work for all github projects.

Back on the server:

    jenkins@maps:~$ cd /tmp/
    jenkins@maps:/tmp$ git clone git@InaSAFEGitHub:timlinux/inasafe.git
    Cloning into inasafe...
    The authenticity of host 'github.com (207.97.227.239)' can't be established.
    RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
    Are you sure you want to continue connecting (yes/no)? yes

Also you should set the Jenkins git user and email:

    jenkins@maps:~$ git config --global user.email "jenkins@linfiniti.com"
    jenkins@maps:~$ git config --global user.name "Jenkins Build Server @Linfiniti2"

### Project setup

Try to do an intial build. It will fail because we have to copy the InaSAFE test data into the job directory. Use the same procedure as above to add ad deploy key to the inasafe-data repo and then clone it (as jenkins user):

    cd ~/jobs/InaSAFE/
    git clone git@InaSAFEDataGitHub:timlinux/inasafe-data.git

### GitHub Hook Setup

In GitHub hooks, enable Jenkins (GitHub plugin) and set the url to:

    http://jenkins.linfiniti.com/github-webhook/

### Testing on Jenkins server

Simply commit something and push it to the server. Turn the speakers on on your desktop with the Jenkins page (http://jenkins.linfiniti.com) open and you should hear a cheer or a groan depending on whether the test passes or fails.

## Further Reading

Here are some useful resources we found while getting things set up.

- http://hustoknow.blogspot.com/2011/02/setting-up-django-nose-on-hudson.html
- http://www.alexconrad.org/2011/10/jenkins-and-python.html
- http://hustoknow.blogspot.com/2011/02/setting-up-django-nose-on-hudson.html
- http://blog.jvc26.org/2011/06/13/jenkins-ci-and-django-howto
- https://sites.google.com/site/kmmbvnr/home/django-jenkins-tutorial (probably the most usful article I found)
- http://blog.mathieu-leplatre.info/django-et-jenkins-fr.html (in French)

### Navigation

- index
- modules
- next
- previous
- Home »
- Contents »
- InaSAFE developer documentation »