...
| Code Block |
|---|
git checkout ${RC_VERSION}-RC
git tag -a "rel-${RC_VERSION}-RC-1" -m "rel-${RC_VERSION}-RC-1"
git push origin --tags |
Optional - Deploy Snapshot Artifacts
If the release candidate is coming off of a "maintenance" branch instead of "develop", it is possible that snapshot artifacts have not been deployed to the Sonatype snapshot repository. If this is the case, Travis will fail to build.
You can check if the snapshot artifacts exist by looking for each module. For example:
| Code Block |
|---|
https://oss.sonatype.org/content/repositories/snapshots/org/vivoweb/vitro-webapp/ |
If the snapshot artifacts do not exist, you can deploy them to Sonatype with the following command:
| Code Block |
|---|
mvn deploy -DskipTests |
Build resources
Once a release has been created, it should be uploaded to GitHub as a Pre-Release. A Pre-Release should be created for jenatools, Vitro, and VIVO. The name should be "Release Candidate 1 - RC_VERSION".
Release Day
Create a new tab in the VIVO modules release plan spreadsheet.