Continuous Integration

Qpid uses the Apache Infrastructure CI service, which is a Jenkins installation. More details are available from the Apache wiki. Builds can run on any operating system instance available, or be locked to a particular type. It may be necessary to restrict some build types to Unix instances only, but using Hudson will give access to Solaris and Windows Server build environments which will be useful for interoperability testing. If a build tool such as Maven is used, even tighter integration with the build process is available, including better test access and the ability to use the Apache Maven repository for publishing artefacts.

Implementation

The implementation of CI for Qpid is being tracked as QPID-3149.

Operation

All builds are prefixed with Qpid- to allow grouping together, the Qpid view shows all jobs matching this pattern.

The following builds are configured:

A timeout of 60 minutes is set for all jobs.

Java Build Configuration

The Java builds use the latest 1.6 release of the JDK, and the latest available Ant version, which are both dependent on the versions available on the Hudson instance running the job.

Only JUnit test results are reported on currently.

The release job archives the following files:

• */release/.zip
• */release/.tar.gz
• */release/maven//.*

Cpp Build Configuration

The following commands are used to perform the Cpp build. They currently include a workaround to allow the build to completed successfully on Ubuntu 12.04.

cd trunk/qpid/cpp

# Workaround QPID-3723 using patch from Fraser Adams
wget https://issues.apache.org/jira/secure/attachment/12509530/fix-explicit-link-problem.patch
cat fix-explicit-link-problem.patch | sed -e 's/qpidtest_PROGRAMS/qpidexectest_PROGRAMS/g'  | patch -t -p1

./bootstrap; ./configure CXXFLAGS="-Wno-unused-result";make clean;make -j4

(As of November 2012, the packages dependencies for Ubuntu 12.04 were: automake, g+, libboost, libboost1.46-dev, libboost-filesystem-dev, libboost-program-options-dev, libicu48, libstdc+6-4.4-dev, libtool, pkg-config, python2.7-dev , python-dev , ruby, sasl2-bin, subversion, uuid-dev).

Python Test Configuration

The following commands are used to run the Python tests:

cd trunk/qpid/python
ulimit -n 1024 # Workaround QPID-3237 - reduce open filehandles
ant -file qpid-python-test-ant.xml -Dqpid.executable=../java/build/bin/qpid-server -Dpython.test.ignore=-I../java/test-profiles/python_tests/Java010PythonExcludes "-Dpython.test.modules=-mqpid_tests.broker_0_10 -m qmf.console" -Dqpid.port=25672 -Dqpid.executable.args="-p 25672 -m 25000" test

Future

Jenkins can be configured to provide many more features with its built-in plugins. These include:

• FIXME/TODO task reporting
• Javadoc publishing
• Coverage reports

The use of these plugins will be investigated once the basic build and test cycle is satisfactorily configured. Future functionality proposed includes:

• Integrate CPP Tests
• Switch CPP Build to use cmake
• Integrate Windows build for Java and CPP Brokers
• Publishing SNAPSHOT versions of Maven artefacts to the Apache repository after a successful nightly build

Notifications

All jobs are configured to send email notifications@qpid.apache.org when a build fails, becomes unstable or returns to stable.

Currently Andrew, Rajith, Robbie and Keith have access to the build configurations.