Project

General

Profile

Continuous Integration with Jenkins

What

The Osmocom Cellular Infrastructure software stack has grown to a size where it make sense to somehow track the state after each commit. The Jenkins Software allows us to do this. The installation can be found at http://jenkins.osmocom.org/jenkins and all of Osmocom is tracked there. The goal is to have all projects/repositories of the osmocom umbrella tracked there.

We are happy if people donate CPU time to be used as additional nodes to execute the compile jobs. Please contact if you want to donate some.

How

We are using Jenkins as it comes from the FreeBSD port system. It runs using the standalone servlet container (Winstone Servlet Engine) and is behind one (IPv6) or two (IPv4) cherokee reverse proxies. Currently there are two nodes FreeBSD 8.2/AMD64 and Debian Squeeze/i386 ( running on the FreeBSD kernel, any weirdness might be a broken syscall implementation).

See also Jenkins_Node_Setup

Custom Build Helper Scripts

If you look into the jenkins job configuration of the individual jobs, you will notice that they use a custom helper script that is part of each Osmocom projects' git repository: contrib/jenkins.sh (for an example, see http://git.osmocom.org/libosmo-netif/tree/contrib/jenkins.sh)

This contrib/jenkins.sh expects that some common helper scripts from http://git.osmocom.org/osmo-ci are in your PATH at the time of execution. The common helper scripts (such as osmo-deps.sh or osmo-build-dep.sh). Those helpers perform tasks similar to all osmocom projects, i.e. clone/update a dependency in the workspace of a build node. The script will try to git-clone, git-fetch, git-reset --hard the dependency.

Building code like jenkins build slave would do it

During development, it sometimes is useful to build the code just like it is built on the jenkins build slave.

If you would like to do that, you should
  1. git clone git://git.osmocom.org/osmo-ci
  2. set your shell PATH to include the osmo-ci/scripts directory
  3. set the MAKE environment variable to your make command (make or gmake)
  4. go to the root directory of the respective project git repo (e.g. libosmo-netif)
  5. execute ./contrib/jenkins.sh

FreeBSD 8.2 and Osmocom

Not everything is required to build on GNU/Linux systems, for SIMtrace a fake libusb-1.0.pc was created to point to the /usr/include,/usr/lib for libusb, all dependencies (fftw, erlang, autotools...) were installed through the port system

Debian/Squeeze

Normal Debian/Squeeze installation, all dependencies installed via the apt/dpkg package system. The arm-elf-gcc toolchain is installed using the toolchain script of the bb.osmocom.org wiki.