Release 1.1.9

notify all stake holders before the release.
confirm svn trunk or branch
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.

put the web servers into maintenance mode (SF WEB, SD WEB)

cd /var/www/html
sudo ./set_eas_mode.sh MAINT

Log onto the SF DB and back up the databases. The exact command line resides in the postgres user crontab.

sudo -u postgres -i
crontab -l
/home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log

Deploy new code to automation server...

C:\apps>c:\apps\eas_automation_update.bat c:\apps\eas_automation

and run the migration to 1.1.9...

python job.py --action EXECUTE --job migrate_to_1.1.9 --env SF_PROD

Web Server

Log into SF PROD WEB and deploy the application as shown here.

# see warning at top regarding branch or trunk
cd /var/www/html
sudo ./deploy_eas_init.sh

Test the application to make sure everything works.

If testing passes, deploy the web app to SD PROD WEB.

# see warning at top regarding branch or trunk
cd /var/www/html
sudo ./deploy_eas_init.sh

Make sure the SD web application works.

You will not be able to log into the web application in SD if DB replication is running.

Put SD PROD WEB server into STANDBY mode

cd /var/www/html
sudo ./set_eas_mode.sh STANDBY_SD

send email to stake holders using automation

python job.py --action EXECUTE --job announce_new_release --env SF_PROD

0 Comments