wiki:BuildProcess

Automated Build Process

Cruise Control

OpenSHA uses CruiseControl for Continuous Integration (see our CruiseControl status page).

Cruise Control is setup on opensha.usc.edu in the /usr/local/cruise/main directory. The configuration file is stored in the repository at conf/cc_conf.xml.

OpenSHA-continuous

This rebuilds the OpenSHA project after every revision, runs select JUnit tests, and sends e-mails when a build is broken.

OpenSHA-nightly

This runs various nightly, time based builds. These run regardless of repository modifications.

OpenSHA-operational

This runs hourly to check the status of key services (GMT map generation, RMI), regardless of repository modifications.

Releasing Applications

see Releasing Applications

Manually Building Nightly Jars

To manually rebuild nightlies, ssh into opensha@opensha.usc.edu, then navigate to the "ant" sub-directory of the Tomcat development build directory (for more information see Tomcat Configuration). This will rebuild all of the nightly jar files, and restart Tomcat:

kevin@milner:~$ ssh opensha@opensha.usc.edu
Last login: Wed Aug 11 13:09:01 2010 from milner.usc.edu
[1:opensha] ~: cd /usr/local/tomcat/default/webapps/OpenSHA_dev/WEB-INF/ant
[2:opensha] /usr/local/tomcat/default/webapps/OpenSHA_dev/WEB-INF/ant: ./runAnt.sh cc-build-test.xml svn.update.app.build
Buildfile: cc-build-test.xml
...
BUILD SUCCESSFUL
Total time: 4 minutes 6 seconds
Last modified 7 years ago Last modified on Aug 11, 2010, 2:08:41 PM