| Version 28 (modified by , 10 years ago) (diff) |
|---|
Introduction
OpenVPN project uses Buildbot (current version 0.8.5) to help increase code quality. Buildbot is a Python application that can work in either master or slave mode. The buildmaster is the core server which accepts connections from buildslaves and tells them what they should do. Typically the clients fetch latest sources and report any build problems to buildbot which in turn informs developers via email. In software engineering this is called Continous integration and helps prevent build problems go unnoticed for extended time periods. The clients (buildslaves) can and should run on a variety of hardware / OS platforms. For the server (buildmaster) the OS choice is largely irrelevant.
As the number of buildslaves can easily get out of hand, the OpenVPN project can make use of your help - see below for details.
Buildbot is described in more detail in the Buildbot manual.
Setting up the VPN connection
Our buildbot (buildmaster) is protected by OpenVPN. To connect your buildslave to it you need:
- Active OpenVPN community services user account
- Properly configured OpenVPN client
- Membership in the appropriate LDAP group
- Certificate authority (CA) key for the VPN
- TLS-auth (TA) key for the VPN
You need to do 1. yourself. The rest will be taken care of for the most part by Samuli, our community manager at openvpn.net. He can also be reached at #openvpn and #openvpn-devel channels as "mattock".
Setting up a buildslave
Overview
Setting up a buildslave requires a few steps:
- Make sure you can build OpenVPN manually
- Install buildbot's requirements
- Download and install buildbot
- Configure buildslave (ask for instructions from samuli)
More details are available in the buildbot manual.
Installing buildbot
Installing buildbot from distro repositories
Many Linux distributions have buildbot in their package repositories. Using the distro version is probably the easiest approach. Buildbot versions 0.7.x and 0.8.x are known to work with our current (0.8.5) buildmaster.
Installing buildbot using easy_install
A fairly easy and somewhat OS-agnostic way to install buildbot is to use easy_install: it should be available your OS'es software repository. Using easy_install will keep buildslave isolated from your OS'es package management and take care of dependencies for you. It is easiest (but not necessary) to run easy_install as root:
First switch to root account, e.g. using sudo or su:
$ sudo -s
Next test that easy_install should work as expected:
$ easy_install -n buildbot==0.8.5
If all went well, install buildbot for real:
$ easy_install buildbot==0.8.5
Once buildslave is installed you can and should switch to an ordinary user account.
Configuring the buildslave
Buildslave configuration is covered thoroughly in the the buildbot manual.
List of existing buildslaves
Here's a comprehensive list of Buildslaves already running (as of Sep 2011). There can be several buildslaves that have the same OS/architecture combination, but this is seldom necessary.
| Operating system | Version | Architecture | 24/7 | Connection tests | Provided by | Notes |
| Arch | - | amd64 | - | Yes | roentgen | |
| Debian | 6 (squeeze) | i386 | No | Yes | mattock | |
| Debian | 7 (wheezy) | i386 | No | Yes | mattock | |
| Ubuntu | 10.04 | amd64 | No | Yes | mattock | |
| Ubuntu | 12.04 | amd64 | No | Yes | mattock | |
| CentOS | 6.x | amd64 | No | Yes | mattock | |
| FreeBSD | 7.4 | amd64 | Yes | Yes | cron2 | ongoing |
| FreeBSD | 8.2 | amd64 | Yes | Yes | cron2 | |
| FreeBSD | 9.0 | amd64 | Yes | Yes | cron2 | |
| OpenBSD | 4.9 | i386 | Yes | Yes | cron2 | |
| NetBSD | 5.1 | amd64 | Yes | Yes | cron2 |
List of build permutations
There are too many to list. However, the builds that use default build flags also trigger connectivity tests.
Troubleshooting
In case your build fails, try running the same build steps manually to see what the problem is.
Source checkout
If you're running into odd problems with buildslave Git checkouts you can try manually running the same commands the buildslave would run. The exact steps can be found from the buildslave's Git logs (in the buildmaster web interface), but they should be similar to these:
$ mkdir /tmp/openvpntest $ cd /tmp/openvpntest $ git init $ git fetch -t git://openvpn.git.sourceforge.net/gitroot/openvpn/openvpn.git +master $ git reset --hard FETCH_HEAD $ git branch -M master
If you're unable to run these commands manually then the buildslave won't be able to do it either.
