Build Stack Job details
You will need the Synapse-Stack-Builder to setup the entire stack for you. This is done by changing the configuration of the Hudson Stack Builder :http://hudson-build.sagebase.org:8081/job/Build%20Staging%20Stack/configure
Look for the section called "Execute Shell", you should see the following properties passed to a shell script:
Clone stack-builder
export CMD_PROPS=\ "-Dorg.sagebionetworks.aws.access.key=<YOUR_AWS_KEY>" \ " -Dorg.sagebionetworks.aws.secret.key=<YOUR_AWS_SECRET_KEY>" \ " -Dorg.sagebionetworks.stack=prod" \ " -Dorg.sagebionetworks.stack.instance=d" \ " -Dorg.sagebionetworks.swc.version=1.10.0-11-g950ee65" \ " -Dorg.sagebionetworks.plfm.version=1.9.0-19-gf672df1" \ echo $CMD_PROPS |
How you set the above properties determines how the stack will be built.
The following table describes what each property is and how it should be set:
Property key | Description |
---|---|
org.sagebionetworks.aws.access.key | The Amazon Web Services access key (id) need to connect to AWS |
org.sagebionetworks.aws.secret.key | The Amazon Web Services secret key (password) need to connect to AWS |
org.sagebionetworks.stack | The name of the stack. This will always be 'prod' when setting up a staging stack. |
org.sagebionetworks.stack.instance | This is the stack letter.The stack letter should always increase so if we are on 'D' then the next should be 'E'. This letter determines which stack you're on. It is VERY important to get this right. |
org.sagebionetworks.swc.version | The version of the portal to be deployed. This version must exist in Artifactory:http://sagebionetworks.artifactoryonline.com/sagebionetworks/simple/libs-releases-local/org/sagebionetworks/portal/ |
org.sagebionetworks.plfm.version | The version of the authorization services to be deployed. This version must exist in Artifactory:http://sagebionetworks.artifactoryonline.com/sagebionetworks/simple/libs-releases-local/org/sagebionetworks/services-repository |
Once you have made the changes to the configuration, press the "Save" button on the bottom of the page. Then click the "Build Now" link to kick off the build. Watch the "Console Output" and verify there are no errors.
The stack builder is designed to be idempotent so it is safe to run it as many times as needed. Each time it runs it attempts to setup the stack exactly as configured.