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 Update version, date, and docs, and push changes back to Github repository release candidate branch
- Push artifacts to staging RAN
- Test that artifacts can be installed
- Items:
...
- 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 - DONE
- Load the synapser library and verify that it works - DONE
- Build docs - DONE
Build Scripts
Besides jenkins.sh, most build scripts can be found here: https://github.com/Sage-Bionetworks/CI-Build-Tools
Workers
These workers are being used to run r packages on different platform. They could be disconnected for various reasons. This section lists the workers and instructions on how to access them. So that one can re-connect the worker when needed.
...
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)
...