DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
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.
...
Build | Trigger | Description |
|---|---|---|
check-in | Tests the Java client with Java broker using the Memory message store. | |
after MMS matrix pass | Tests the Java client with Java broker using BDB message store. | |
every 24h | Tests the Java client with Java broker using Derby message store. | |
check-in | Tests the Java client with the C++ Broker. | |
every 24h | Tests the Java client with Java broker under IBM JDK 1.6. AMQP 0-10 only. | |
every 24h | Tests the Java client with Java broker under Sun JDK 1.7. AMQP 0-10 only. | |
every 24h | Tests the Python client with the Java Broker against AMQP 0-8. 0-9. and 0-10 protocols.. | |
every 24h | Tests the Python client with the C++ Broker. | |
every 24h | 0.16 Release branch test. Tests the Java client with Java broker. AMQP 0-10 only. | |
every 24h | Generates binary release archives and Maven artefacts for the Java Client/Broker. |
...