Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is a draft. TODO: update links to Sage builds.

This document records the Jenkins builds set up for synapser dev/staging/validation/release.

Table of Contents
outlinetrue

Build Items

Dev Build

Staging Build

Release Build

Future Work

  • Append an item to run right after release build item, testing the deployment:
    • Download and install the artifacts on different platform and versions of R
    • Load the synapser library and verify that it works (by running the integration tests)

Workers

Windows

URL: http://jenkins.sagebase.org:8080/computer/jenkins-windows-slave/

Location

The EC2 machine is under the AWS account aws-it@sagebase.org
The password to the AWS account is on Belltown /work/platform/PasswordsAndCredentials/AWS-ITCredentials/passwords.txt

The machine name is jenkins-slave-windows-2017-Sep-29
As seen in the AWS console the address is 34.215.128.118
The region is US West (Oregon)

Access

  1. To log in, first get the password
    • Click Actions > Connect > Get Password
    • Enter the contents of  /work/platform/PasswordsAndCredentials/AWS-ITCredentials/awsit-keypair-west.pem
  2. Install Microsoft Remotes Desktop client
  3. Chose New, and enter the following:
    • PC Name:  enter IP address
    • User name:  Administrator
    • Password:  As returned by AWS
You can now connect to the slave.

Ubuntu

Access

Here is the entry for your ~/.ssh/config

Mac

Access

Here is the entry for your ~/.ssh/config
  • Host georgetown
  • user sagebio
  • HostName 140.107.149.88
  • password is on Belltown /work/platform/PasswordsAndCredentials/AWS-ITCredentials/passwords.txt

To restart, run the following command seen on the page:
 
java -jar slave.jar -jnlpUrl http://ec2-54-245-172-65.us-west-2.compute.amazonaws.com:8080/computer/georgetown.fhcrc.org/slave-agent.jnlp -secret xxxx &

Note, the "&" keeps the process running after you disconnect.