...
Schema/User | Database | Purpose |
|---|---|---|
OLEDBA | Test Oracle | Master data source for OLE development. Extracted nightly and stored into https://svn.kuali.org/repos/ole-cfg-dbs/trunk/development |
OLELOCAL | Test Oracle | Database schema for developer work. Refreshed nightly from https://svn.kuali.org/repos/ole-cfg-dbs/trunk |
OLEDEV | Test Oracle | Database schema for the |
OLECI | Test Oracle | Database schema for the OLE unit tests. Refreshed nightly from https://svn.kuali.org/repos/ole-cfg-dbs/trunk |
Continuous Integration
OLE Uses Hudson (http://hudson-ci.org/) both to run testing suites as well as manage the deployment of the OLE Testing servers and refreshing of the database instances. While Hudson has the hooks for running unit tests, it also serves as a web-based scheduling console which can run shell scripts, Ant scripts, and Maven.
Reference Jobs:
Server Controls
The jobs within Hudson utilize the Amazon-provided command-line tools to create and destroy the servers. Amazon has a lot of documentation on these tools at: http://docs.amazonwebservices.com/AWSEC2/latest/CommandLineReference/
Reference Jobs:
- Template-Check-Instance-Status
- Template-Launch-EC2-Server
- Template-Start-Instance
- Template-Stop-Instance
Tomcat Server Deployment / Control
Hudson jobs are also used to build and deploy the OLE application to the test servers. They can also be used to start and stop the tomcat instance as needed.
Reference Jobs:
Database Schema Refreshes
| Note | ||
|---|---|---|
| ||
|
...
- EC2
- Creation and termination of instances. (Much of this is automated through Hudson.)
- RDS
- Amazon MySQL database service - creation, deletion, and snapshots of instances.
- S3
- Amazon storage service. Used to store OLE releases and (indirectly) EC2 and RDS instance snapshots.