Page Comparison

This is a reverse-chronological log of all work done in the platform AWS account.

...

1. Point Hudson build 'Project SwC-release' to SWC branch release-1.2
2. Update root pom.xml on that branch to 1.2.4-RC and build.
3. Check that .war appears on http://sagebionetworks.artifactoryonline.com/sagebionetworks.
4. Upload .war to S3 using SynapseDeployer (TODO: Clearly document dependencies to get this working on any system.)
   
   1. Modify Synapse-Repository-Services/tools/SynapseDeployer/main.py (version and env_to_upgrade)
   2. run main.py
5. Deploy on portal-prod-b-test environment in AWS console
6. Point Hudson build back to branch release-1.3
7. Test upload file using test portal 
   
   1. Login, goto to on of my entities, create data entity, upload file, create data entity, upload file. ==> OK
8. Deploy 1.2.4-RC on prod-b-portal (07/25, 10:18am)-prod-b-test environment in AWS console
9. Point Hudson build back to branch release-1.3
10. Test upload file using test portal 
    
    1. Login, goto to on of my entities, create data entity, upload file, create data entity, upload file. ==> OK
11. Deploy 1.2.4-RC on prod-b-portal (07/25, 10:18am)

07/24/2012

• Deal with aftermath of PLFM-1399 (rollback to ProdB)
• Finalize changes to PLFM-release build
• Start looking at closing Synapse-Repository-Services/release-1.2 and SynapseWebClient/release-1.3 branches

07/25/2012

• Close Synapse-Repository-Services/release-1.2 and SynapseWebClient/release-1.3 branches

  Code Block
  language bash title Merge SWC-release branch
  git clone https://github.com/Sahe-bionetworks/SynapseWebClient.git git checkout release-1.3 git tag 1.3.1 git checkout develop git merge release-1.3 # Fix conflict on pom.xml (version must be develop-SNAPSHOT) git add pom.xml git commit -m "Merged release-1.3" git checkout master git merge release-1.3 # Fix conflicts git add pom.xml git commit -m "Merged release-1.3"

• Modify SWC builds on Hudson to use generate the version from git tag (same as repo service builds)

  • In Hudson, find SWC-release build.
    • Configure
      • In git section, Advanced: check 'Skip Internal Tag' so Hudson does not overwrite our tag
      • In Build section, add an Execute Shell step with following command:

chmod 777 pomSnapshotToLastGitTag.sh
./pomSnapshotToLastGitTag.sh

• • • • In Git/Branches to build, specify release-1.4 (NOTE: This step is part of the weekly routine)
        
        
• Create Synapse-Repository-Services/release-1.3 and SynapseWebClient/release-1.4 branches
• Deploy 1.3/1.4 artifacts on prodC and migrate data from prod to prodC

07/26/2012

• Build and deploy fixes for PLFM-1390 and PLFM-1399.
  
  • Tag and push with tags to build 1.3.1-RC and 1.4.1-RC
  • Upload and deploy on prodC

Finalize prod-c deployment by Xa on 2012/07/23

...

1. Since the deployment script is broken (see:

   Jira Legacy
   server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1351

   ), I manually uploaded the war files (Upload in the AWS  Web Console has been fixed!):
   
   1. services-repository-1.0.1.war
   2. services-authentication-1.0.1.war
   3. portal-1.0.2.war
2. Deployed the respective wars to Synapse prodA.
3. I was unable to run the smoke tests on prod-a due to

   Jira Legacy
   server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1352

   .

Update prod to 1.0.0 on stack A by Xa on 6/20

...

1. Stop prodBSearchUpdater
2. Drop and re-create prodB schema
3. Restart App repo-prod-b on AWS
   • tables are not being created
     • looking at tomcat logs, looks like the app did not terminate in time
     • tried restart again but it looks like app not responding
   • try rebuild env to force shutdown of tomcat
     • had to do it a couple if times, no idea why failed the first time...
4. Start migration from Prod to ProdB
   • Migration took about 1.5hr
   • Put repo in RO mode
5. Getting 'An error occured trying to load' from portal when trying to display entity (tried 4492, 4494, 4496)
   • Does not look like a repo issue, I can get the entities from Python
   • Cannot login using Google account (error from auth) or Sage account (says I'm not authenticated)
     
   • Can login from Python
6. Restart App for portal and auth
   • No change
7. Log into auth/portal EC2 to look at logs
   • Nothing special in auth
   • After getting error msg about load failure, following msg in portal log:
     "Cannot find user login data in the cookies using cookie.name=org.sagbionetworks.security.user.login.data" >> Normal since I did not login?
   • No log entry on login failure
   • ~2:30am: Timeouts from repo (maybe connected to instance being removed)
8. Put repo back in RW mode

...