Page Comparison

This document records the Jenkins builds set up for synapser dev/staging/validation/release and information about the workers that are used for the builds.

...

• Run on release candidate branches, ideally once; and occasionally, when a patch need to go in before release.
• Build the artifacts
• Do not make change to Github repository
• Push artifacts to staging RAN
• Test that artifacts can be installed
• Items:
  • http://jenkins.sagebase.org:8080/job/synapser-staging/
  • http://jenkins.sagebase.org:8080/job/synapser_staging_artifact/
  • http://jenkins.sagebase.org:8080/job/synapser_staging_deploy/
  • http://jenkins.sagebase.org:8080/job/synapser_check/

Release Build

• Run when a version is released. 
• Do not make change to Github repository
• Push artifacts to RAN
• Test that artifacts can be installed
• Item:
  • http://jenkins.sagebase.org:8080/job/synapser_prod_deploy/
  • http://jenkins.sagebase.org:8080/job/synapser_check/

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)

...

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)

...