-
Notifications
You must be signed in to change notification settings - Fork 17
Release Process
riedelcastro edited this page Sep 27, 2014
·
2 revisions
- First merge master into development (to fix conflicts in the dev branch)
- Then check out master
git checkout master
- Now merge development branch into master (shouldn't create conflicts due to step above)
git merge dev
- Now instantiate the release process using the sbt release plugin
sbt release
- This requires entering new coordinates (versions)
- It would also require that you have credentials to upload to homeniscient.
- Sometimes errors happen during publishing. Uploading again causes more problems. Need to remove artefacts from nexus (http://homeniscient.cs.ucl.ac.uk:8081/nexus/index.html#welcome).
- Uploading is really slow due to the example data.