Continuous Integration

Qpid uses the Apache Infrastructure CI service, which is a HudsonJenkins installation. See here for more details.

Implementation

The implementation of CI for Qpid is being tracked as QPID-3149 and will be completed during the 0.11 development stream.

Operation

All builds are prefixed with either qpid- to allow grouping together. The proposed build entries are as follows:

• qpid-java-build - triggered by check-ins to subversion
• qpid-java-system-tests - nightly
• qpid-cpp-build - triggered by check-ins to subversion
• qpid-cpp-system-tests - nightly
• qpid-python-tests - nightly
• qpid-release-build - nightly or weekly

The initial testing of the CI configuration is being carried out under Qpid Java Build until any issues are sorted out. Currently, failover seems to be a problem.

• https://builds.apache.org/hudson/job/Qpid%20Java%20Build/ws/trunk/qpid/java/build/results/systests/TEST-org.apache.qpid.test.unit.ack.AcknowledgeAfterFailoverOnMessageTest.testAutoAck.err

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

Monitoring

I propose creation of a new mailing list, qpid-build@apache.org which would receive a copy of all output from every CI build. Additionally, the results of failing builds should be mailed to committers that checked in the breaking changes, and a nightly (or weekly) summary from the release build should be sent to the qpid-dev list.