- A week before the scheduled release, create a ticket for the application integration team: help.mit.edu, create a ticket for isda-admin. Include the desired date for the release (note that this should be a tuesday or a wednesday), and the path where ops team should expect to find the .war file for the release. This is typically a directory you create on isda-thalia1 in isdasnap's home directory, using the naming convention sprintXX-release-monthday where month-day should be the month-day of proposed release. Example: /home/isdasnap/sprint6b-release-july1.
- The morning of the release day, ssh to isda-thalia1.mit.edu.
- ssh -l isdasnap isda-thalia1.mit.edu
- If you have not already created a directory, do so now (see #1 for naming convention).
- cd into that directory, and checkout the ui from the branch to be released
- svn co svn+ssh://svn.mit.edu/zest/thalia/ui/branches/thalia-UI1.0-sprintXX ./ui
- Then checkout the ime from the branch to be released
- svn co svn+ssh://svn.mit.edu/zest/thalia/ime/Branches/thalia1.0-sprintXX ./ime
- cd into the ui directory, and compile:
- mvn compile
- cd into the ime directory, and create the war file:
- mvn clean package -Denv=prod1 -Dincludeui=true -Duipath=/home/isdasnap/<directory-for-release>
- cd into the ime/target directory, to be sure ROOT.war has been created.
- Then check the webserviceclient.properties file in ime/target/WEB-INF/classes/alfresco/webserviceclient.properties, and make sure that the alfresco repository is pointing to isda-thalia6
- Email Hunter, or whoever on the application integration team is doing the release, to confirm location of the war file.
- Release is generally done after 6:30 pm. Its a good idea to be available online, in case ops have any questions.
Overview
Content Tools
Activity