...
- notify all stake holders before the release.confirm svn trunk or branch
- vcs path: branches/1.1.9
- 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.
...
Deploy new code to automation server.
Pull from branches/1.1.9.
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 |
|---|
C:\apps>c> del c:\apps\eas_automation\automation > del c:\apps\eas_automation\database REM copy c:\apps\eas_automation_setup.bat to c:\apps\eas_automation_setup_1.1.9.bat REM edit c:\apps\eas_automation_setup_1.1.9.bat > c:\apps\eas_automation_updatesetup_1.1.9.bat c:\apps\eas_automation |
...
| Code Block |
|---|
cd /var/www/html sudo svn export http://eas.googlecode.com/svn/trunk/branches/1.1.9/web/bin/deploy_eas_init.sh ./deploy_eas_init.sh sudo ./deploy_eas_init.sh |
...
If testing passes, deploy the web app to SD PROD WEB.
| Code Block |
|---|
# see warning at top regarding branch or trunk cd /var/www/htmlcd /var/www/html sudo svn export http://eas.googlecode.com/svn/branches/1.1.9/web/bin/deploy_eas_init.sh ./deploy_eas_init.sh sudo ./deploy_eas_init.sh |
...