Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated page with new information from DuraSpace Bamboo setup

...

Definition of Continuous Integration (CI): Martin Fowler

Currently Johns Hopkins DuraSpace 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, Whenever a new checkin occurs to DSpace SVN, DuraSpace's 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.

When a build fails, an email is automatically sent to the 'dspace-changelog' listserv to notify the developers & committers. Once the problem is fixed, a 'build successful' email will be sent to the same listserv.

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

DSpace 1.x

DSpace 2

DSpace 2

  • Currently not configured in DuraSpace Bamboo.

Configuration

DSpace 1.x

  • Bamboo polls trunk and the 1.5.x branchseveral locations in DSpace SVN
  • Maven 2.02.8 1 is used to build the projects
  • The Maven command used is
    Code Block
    mvn clean test compile package -Pdistributions,allPaddons
  • Sun Java 1.5.0_13 6 is used
  • Build reports could be emailed send emails 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
    Code Block
    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

...

  • 'dspace-changelog' listserv on each failure, and on the first successful build after a failure.