| Table of Contents |
|---|
Preamble
- notify all stake holders before the release.
- vcs path: branches/1.2.0
- execute all steps in the SF ENVs first and test the application.
- if tests pass, then execute steps on SD ENVs.
- In the unlikely event that things go very badly, we switch over to the old application in SD.
Web into MAINT Mode
put the web servers into maintenance mode (SF WEB, SD WEB)
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh MAINT |
Database Backup
Log onto the SF DB and back up the databases. The exact command line resides in the postgres user crontab.
| Code Block |
|---|
sudo -u postgres -i crontab -l /home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log |
Automation
Deploy new code to automation server.
Pull from branches/1.2.0
One way to do this is to edit c:\apps\eas_automation_setup.bat.
We should one day paramterize this bat file (or move to python).
...
| Code Block |
|---|
python job.py --action EXECUTE --job migrate_to_1.2.0 --env SF_PROD |
Schedule and enable the address_change_report to run every week day at 0755.
Use an existing scheduled item to crib from.
Enable the parcels ETL which have been disabled because of this bug.
Deploy Geoserver Configurations (SF)
We've removed the invalid addresses layer from from geoserver which means we need to deploy those configurations. Adjust SVN paths to branches/1.2.0.
| Code Block |
|---|
cd /usr/share/apache-tomcat-7.0.32/ sudo vim ./deploy_geoserver_init.sh # MAKE THESE CHANGES # JIRA_SVN_PATH=branches/1.2.0 # GOOGLE_CODE_SVN_PATH=branches/1.2.0 sudo ./deploy_geoserver_init.sh |
Deploy App To Web (SF)
Log into SF PROD WEB and deploy the application as shown here.
In this release we use new deploy code so the steps are slightly different.
You should notice Notice that command line interface has been simplified.
| Code Block |
|---|
cd /var/www/html svn export http://eas.googlecode.com/svn/branches/1.2.0/web/bin/deploy_eas_init.sh ./deploy_eas_init.sh sudo ./deploy_eas_init.sh branches/1.2.0 branches/1.2.0 pmccullough |
Test the application to make sure everything works.
Deploy to SD
If testing in SF passes, deploy the web app to SD PROD with steps parallel to SF PROD (WEB and GEO).
...
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_SD |
Release Notifications
- remove 1.2.0 from road map
- publish blog post
send email to stake holders using automation
Code Block python job.py --action EXECUTE --job announce_new_release --env SF_PROD
Done!
...