Page History

...

All builds are prefixed with qpid- to allow grouping together, the Qpid view shows all jobs matching this pattern. The proposed build entries are as follows:

...

The initial testing of the CI configuration is being carried out under Qpid Java Build using the qpid-java-build job only, until any issues are sorted out.

...

At present, these tests run a single profile, such as default or java.0.10. As the number of profiles increases, it may be better to use the Hudson matrix project feature to paramaterise the system test build around the test profile names.

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

Future

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

...

• 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

This appears to be caused by spaces in the job name. A copy of the original job named qpid-java-build works as expected.

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 and/or interop test builds should be sent to the qpid-dev list.

...