Thalia has two pieces: the IME back end, which is a Java .war file, and the .swf front end, which is written in OpenLazlo.
ARE YOU DOING A RELEASE?
Before deploying anything, confirm that you won't interrupt anyone else's work.
- For all releases, check in on jabber chat thalia-talk .
- For QA releases, also check in with QA testers in thalia-QA .
- For production releases, email asst@mit.edu about the scheduled down time ahead of time so they will not be alarmed when the nagios service fails on Thalia.
COMMON STEPS:
1. Make sure all developers have checked in their code.
BACK END
Configuring the Build Environment
...
svn commit
5. Deploy the war:
a. Check that it's ok to deploy. Start in the thalia-talk chat . If deploying to QA, check in with the QA contractor in thalia-qa . If deploying to production, you will already have emailed asst@mit.edu about the scheduled down time ahead of time so they will not be alarmed when the nagios service fails on Thalia.
b a. By default, Thalia will deploy to isda-thalia-1.mit.edu . Edit Branches/branchname/pom.xml to specify a different location. Check the Thalia Environments list for the correct server.
bc. To specify tomcat authentication info in Maven, add the following line in settings.xml in $M2_HOME/conf/settings.xml
<server>
<id>deploymentserver</id>
<username>username</username>
<password>password</password>
</server>
cd. Deploy with Maven:
mvn tomcat:deploy