Release Instructions

Sites
a.k.a Landing Pages or Micro-sites <Hollywood Servers> SVN1: /microsites/<client name> Revisions - 29650

Lead Bin 5
a.k.a Stingray and LB5 <Seville Servers> SVN1: /svn.datamark.com/stingray Revisions - 9000
1

Client
SVN : stingray/client

System (Core)
SVN : stingray/system
1

nSite
a.k.a Siphon SVN : /siphon Revisions - 850
1

Sitebin
a.k.a Anemone SVN : /anemone Revisions - 115
1

Stingray Tools
SVN1: /stingray/tools

Revisions - 9000

Scripts
svn.datamark.com/dtmk

1 For all SVN Locations the following prefix will be assumed: http://svn.datamark.com Release Instructions: Version 1.0 February 29, 2012 Page Number 1 of 8

Instructions for updating nSite

1

Updating QA
STEP 1: Moving code to Release Candidate. Servers: mesquite.datamark.com Path: /home/webdocs/siphon/release_candidate STEP 2: Building new version based on Step 1 Servers: qa1seville.datamark.com qa2seville.datamark.com Path: Doesnt matter Command: 1) sudo deploy_siphon.sh -e qa Commands: 1) eligible trunk 2) merge trunk <revision number(s)1> 3) commit

Updating Staging
STEP 1: Moving code to Staging. Servers: mesquite.datamark.com Path: /home/webdocs/siphon/staging

Commands: 1) eligible release_candidate 2) merge release_candidate <revision number(s)1> 3) commit

STEP 2: Building new version based on Step 1 Servers: stseville.datamark.com Path: /srv/siphon Command: 1) sudo deploy_siphon.sh -e staging

Updating Production
STEP 1: Moving code to Production. Servers: mesquite.datamark.com Path: /home/webdocs/siphon/production Commands: 1) eligible 2) merge1 <revision number(s)> 3) commit 4) tag 5) push_siphon.sh -N <Tag Number>

nSite Push Instructions Revision 3 12/9/2011

1 Command Example: merge 473 474 478 Do not use the format of -r

Page Number 2 of 8

Instructions for Updating Stingraytools

Update to QA
STEP 1: Moving code to Release Candidate. Servers: mesquite.datamark.com Path: /home/webdocs/stingray-tools/release_candidate STEP 2: Building new version based on Step 1 Servers: QA1Seville OR QA2Seville Path: Doesnt Matter Command: 1) sudo stingraytools_qa_setup.sh Commands: 1) eligible 2) merge1 <revision number(s)> 3) commit

Update to Staging
STEP 1: Moving code to Staging. Servers: Mesquite Path: /home/webdocs/stingray-tools/staging STEP 2: Building new version based on Step 1 Servers: stseville.datamark.com Path: Doesnt Matter Command: 1) sudo deploy_stingraytools.sh -e staging Commands: 1) eligible 2) merge1 <revision number(s)> 3) commit

Update to Production
STEP 1: Moving code to Production. Servers: Mesquite Path: /home/webdocs/stingray-tools/production Commands: 1) eligible 2) merge1 <revision number(s)> 3) commit 4) tag 5) push_stingraytools.sh -N<Tag Number>

1 Command Example: merge 473 474 478 Do not use the format of -r

Stingray-Tools Push Instructions Revision 3 12/12/2011

Page Number 3 of 8

Instructions for Updating LB5 - Client

1

QA Test and Review

STEP 1: Moving code to QA Servers: qa1seville.datamark.com qa2seville.datamark.com Path: root STEP 2: Picking up Client Revisions Servers: qa1seville.datamark.com qa2seville.datamark.com Path: /srv/stingray/www/classes/client Commands: 1) eligible 2) merge <revision number(s)1> 3) commit Commands: 1) sudo stingray_qa_setup

Update to Staging
STEP 1: Updating Staging with new Revisions. Servers: mesquite.datamark.com Path: /home/webdocs/stingray-client Commands: 1) svn up 2) eligible 2) merge <revision number(s)1> 3) commit

STEP 2: Updating Staging with new Revisions. Servers: mesquite.datamark.com Path: /home/webdocs/stingray-system

Commands: 1) staging_push_stingray.sh -N (`latest_tag2` OR current version Get the Version Number from Staging)

Updating Production
STEP 1: Pushing Client Code to Production Servers: mesquite.datamark.com Path: /home/webdocs/stingray-system 1 - Do not use the format of -r Command Example: merge 473 474 2 - Please Note: When you use the parameter `latest_tag` you must be LB5 Client Push Instructions in the: /home/webdocs/stingray-system folder on Mesquite. Page Number 4 of 8 If you are not in this folder, you will receive an error. Revision 1 12/9/2011

Commands 1) push_stingray.sh -N (`latest_tag2` OR Current Version)

Instructions for Updating LB5

Update to QA
STEP 1: Moving code to Release Candidate. Servers: qa1seville.datamark.com Qa2seville.datamark.com Path: root STEP 2: Picking up System Revisions Servers: qa1seville.datamark.com qa2seville.datamark.com Path: /srv/stingray/www Commands: 1) sudo stingray_qa_setup

Commands: 1) eligible 2) merge <revision number(s)1> 3) commit

Update to Staging
STEP 1: Updating Staging with new Revisions. Servers: mesquite.datamark.com Path: /home/webdocs/stingray-system Commands: 1) eligible release_candidate 2) merge release_candidate <revision number(s)1> 3) commit 4) tag 5) staging_push_stingray.sh -N <Version in Staging>2

Updating Production
STEP 1: Pushing Code to Production Servers: Mesquite.datamark.com Path: /home/webdocs/stingray-system Commands 1) stingray_push.sh -N`latest_tag`2

1 - Command Example: merge 473 474 478 Do not use the format of -r 2 - Please Note: When you use the parameter `latest_tag` you must be in the /home/webdocs/stingray-system folder on Mesquite. If you are not in this folder, you will receive an error dialog. Updating LB5 - System Revision 1 12/9/2011 Page Number 5 of 8

Instructions for Updating Microsites

1

Update to QA
STEP 1: Moving code to QA Servers: qa1hollywood.datamark.com OR qa2hollywood.datamark.com Path: /home/webdocs Command: 1) sudo up <client name>

Update to Staging
STEP 1: Moving code to Staging Servers: mesquite.datamark.com Path: /home/webdocs/<client name> Commands: 1) svnmerge.py avail1 2) svnmerge.py merge -r2 <revision number(s)> 3) commit3 4) staging_syncdir .

Update to Production
STEP 1: Moving code to Production Servers: mesquite.datamark.com Path: /home/webdocs/<client name> Commands: 1) syncdir .

1 Make sure the revisions are available to BE pushed 2 Command Example: svnmerge.py merge -r29000,29001, 29002 3 Make sure there are no conflicts before doing the commit

Microsite Push Instructions Revision 2 3/6/2012

Page Number 6 of 8

Instructions for Updating Sitebin

Update to QA
STEP 1: Moving code to Release Candidate. Servers: qa1seville.datamark.com qa2seville.datamark.com Path: /srv/anemone STEP 2: Picking up new Revisions Servers: qa1seville.datamark.com qa2seville.datamark.com Path: /srv/anemone/www Commands: 1) svnmerge.py avail 2) svnmerge.py merge <revision number(s)1> 3) commit Commands: 1) sudo anemone_qa_setup.sh

Update to Staging
STEP 1: Moving code to Staging Servers: Mesquite Path: /home/webdocs/anemone Commands: 1) svn up 2) svnmerge.py avail 3) svnmerge.py merge <revision number(s)1> 3) commit 4) tag 5) push_anemone.sh -N <tag #>

STEP 1: Deploying the code to Staging Servers: stseville.datamark.co Path: /srv/anemone Commands: 1) sudo anemone_live_setup.sh -N <Tag # >

Update to Production
STEP 1: Moving code to Production Servers: Mesquite Path: /home/webdocs/anemone Commands: 1) svnmerge.py avail 2) svnmerge.py merge <revision number(s)1> 3) commit 4) tag 5) push_anemone.sh -N <tag #>

1 Make sure the revisions are available to BE pushed

Microsite Push Instructions 2 Command Example: svnmerge.py merge -r29000,29001, 29002 3 Make sure there are no conflicts before doing the commit Revision 1 2/28/2012

Page Number 7 of 8

Instructions for Updating Import Scripts

1

Update to QA

STEP 1: Moving code to Release Candidate. Servers: qaboston.datamark.com Path: /srv/

Commands: 1) sudo anemone_qa_setup

STEP 2: Picking up new Revisions Servers: qa1seville.datamark.com qa2seville.datamark.com Path: /srv/anemone/www Commands: 1) svnmerge.py avail 2) svnmerge.py merge <revision number(s)1> 3) commit

Update to Staging

STEP 1: Moving code to Staging Servers: stseville.datamark.co Path: /srv/anemone Commands: 1) sudo anemone_live_setup <Version # >

Update to Production
STEP 1: Moving code to Production Servers: Outlook Path:

Commands: 1) - Submit a Help Desk ticket requesting that revision(s) number(s) (number) be pushed to Production.

1 Make sure the revisions are available to BE pushed 2 Command Example: svnmerge.py merge -r29000,29001, 29002 3 Make sure there are no conflicts before doing the commit

Microsite Push Instructions Revision 1 2/28/2012

Page Number 8 of 8