Details
-
Type: Improvement
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:4
-
Sprint:B - Summer 2018
Description
When we release a new version of IGB to users, we need to update the project's on-line repository with newly built jar files.
This is required to support App developers and others.
The current Nexus repositories used by the IGB project are hosted under eos.transvar.org/nexus and are using out-of-date Sonatype Nexus software.
To-do:
- Set up a new Nexus repository using latest Nexus software DONE
- Set up user-friendly address for new Nexus host (nexus.bioviz.org) DONE
- Migrate legacy artifacts from old Nexus host (eos.transvar.org) to simple hosting by Apache, back them up DONE
- Develop, deploy, test backup strategy for above items
- Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts
- Document all of the above
Attachments
Issue Links
- relates to
-
IGBF-1419 Add new Nexus repository to top-level POM.xml
- Closed
Address for apache host for artifacts up to IGB-9.0.0:
maven.bioviz.org
Address for nexus 3 repository with artifacts from 9.0.1:
nexus.bioviz.org
Configured 3 repositories with legacy artifacts and added to pom.xml.
TESTING:
1. After putting Apache-hosted maven repositories into service, review the logs for errors or warnings.
2. Make a branch of the IGB repository that replaces all mention of eos.transvar.org with the new hosts.
3. Move your local .m2 directory (to trigger re-download of artifacts)
4. Build all IGB locally - check for errors.
5. Build IGB Apps (Deepti's BioJava App demo, ProtAnnot)
6. Push the branch to the fork and make sure the project builds under bitbucket pipelines