| 1 | = Automated Build Process = |
| 2 | |
| 3 | == Cruise Control == |
| 4 | |
| 5 | OpenSHA uses [http://cruisecontrol.sourceforge.net/ CruiseControl] for [http://en.wikipedia.org/wiki/Continuous_integration Continuous Integration] (see [http://opensha.usc.edu:8080/cruisecontrol/ our CruiseControl status page]). |
| 6 | |
| 7 | Cruise Control is setup on opensha.usc.edu in the /usr/local/cruise/main directory. The configuration file is stored in the repository at [source:conf/cc_conf.xml]. |
| 8 | |
| 9 | === OpenSHA-continuous === |
| 10 | This rebuilds the OpenSHA project after every revision, runs select JUnit tests, and sends e-mails when a build is broken. |
| 11 | |
| 12 | === OpenSHA-nightly === |
| 13 | This runs various nightly, time based builds. These run regardless of repository modifications. |
| 14 | * 12:00am - Nightly application jar builds |
| 15 | * 1:45am - Runs nightly test suite, updates [http://opensha.usc.edu/cobertura/ Cobertura Code Coverage] |
| 16 | * 2:00am (Sun/Thurs only) - Runs complete test suite, updates [http://opensha.usc.edu/cobertura/ Cobertura Code Coverage] |
| 17 | |
| 18 | === OpenSHA-operational === |
| 19 | This runs hourly to check the status of key services (GMT map generation, RMI), regardless of repository modifications. |