DSpace Continuous Integration

Definition of Continuous Integration (CI): Martin Fowler

Currently Johns Hopkins uses Bamboo , a CI product from Atlassian, makers of Jira and Confluence. The support JHU provides for this service is "best effort".

How it is done

The DSpace Sourceforge Subversion repository is polled each hour for changes (commits). If the repository has changed, Bamboo will check out the project and attempt to build it, logging the success or failure of the build. If the build succeeds, the build artifacts (jar files, war files) will be saved for a period of time.

The build reports are available on the web as a traditional website or as RSS feeds:

DSpace 1.x

• Browse all DSpace 1.x builds
• Trunk build reports (feed)
• 1.5.x branch build reports (feed)
• Language Pack (feed)
• Language Pack (XMLUI) (feed)
• Contrib RDF (feed)
• Contrib RDF (XMLUI) (feed)
• Contrib Embargo API & DSpace Impl (feed)

DSpace 2

• Browse all DSpace 2 builds
• Trunk build reports (feed)

Configuration

DSpace 1.x

• Bamboo polls trunk and the 1.5.x branch
• Maven 2.0.8 is used to build the projects
• The Maven command used is

  mvn clean test compile package -Pdistributions,all

• Sun Java 1.5.0_13 is used
• Build reports could be emailed to dspace-devel if we so choose. Right now they go to my inbox.

DSpace 2

• Bamboo polls DSpace 2 trunk
• Maven 2.0.9 is used to build the projects
• The Maven command used is

  mvn clean test

• Sun Java 1.5.0_16 is used
• Failed builds (followed by the first successful build) are emailed to dspace-architecture.
• Build artifacts are not being saved currently.

Future Work

We plan to download the build artifacts on a nightly basis, and automatically deploy the build artifacts to a test server, say nightly.dspace.org. The goal is to ensure that the build artifacts are viable (e.g. the xmlui war is packaged properly), and to test the deployment process.