Background
The Github repository for the R client has two main branches, "develop" and "master". "Master" contains the series of released versions of the R Client, each tagged according to its version. "Develop" is the branch for on-going development work. It is merged into Master when a new version is released.
Builds are done using Jenkins jobs which run at http://jenkins.sagebase.org:8080. There are jobs for (1) building the client from the Github repository, (2) deploying clients to Sage's LRAN (depot.sagebase.org) and (3) for testing versions deployed to the LRAN.
Deployment Steps
To deploy a new version of the R client to depot.sagebase.org and verify that it runs againt production Synapse:
- clone Sage-Bionetworks/rSynapseRepository
- switch to the develop branch
git checkout develop
- set the version for the new release, by editing the "Version:" field in the DESCRIPTION file. Also update "Date:" to be the current date and fill in "ReleaseNotes:" with a brief description of the main features or fixes which are included in the new version. Edit man/synapseClient-package.Rd, ensuring its Version and Date fields match those in the DESCRIPTION file.
...
Note: The specifics will change as newer version of R are released.
How to Black List a Version
If a version of the R Client is problematic or incompatible with a version of the Synapse server, there is a mechanism to disable or "black list" that version of the client.
...
Verify that the file has been modified correctly: Run the integration test suite in Jenkins, as described above. This will exercise the black list, ensuring correctness.
References
R documentation
...
bash
Jenkins
...