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
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Ann Loraine [ aloraine ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Deepti Joshi [ djoshi4 ] |
| Summary | document how to update project maven repository with new artifacts | document how to update on-line maven repository with new artifacts |
| Summary | document how to update on-line maven repository with new artifacts | document and update on-line maven repository |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. We will: * Set up a new Nexus repository using the latest software from Nexus * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases |
| Story Points | 2 | 4 |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. We will: * Set up a new Nexus repository using the latest software from Nexus * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. We will: * Set up a new Nexus repository using the latest software from Nexus * Determine user-friendly address for above (nexus.bioviz.org or mvn.bioviz.org ?) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. We will: * Set up a new Nexus repository using the latest software from Nexus * Determine user-friendly address for above (nexus.bioviz.org or mvn.bioviz.org ?) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Determine user-friendly address for above (nexus.bioviz.org or mvn.bioviz.org ?) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Determine user-friendly address for above (nexus.bioviz.org or mvn.bioviz.org ?) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. We will: * Set up a new Nexus repository using the latest software from Nexus * Determine user-friendly address for above (nexus.bioviz.org or mvn.bioviz.org ?) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. We will: * Set up a new Nexus repository using the latest software from Nexus * Determine user-friendly address for above (nexus.bioviz.org or mvn.bioviz.org ?) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrated legacy artifacts from previous repository to new one, including IGB artificacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. To-do: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. **To-do**: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. **To-do**: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. *To-do*: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. *To-do*: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for above (nexus.bioviz.org) * Assign URL nexus.bioviz.org to the new Nexus repository * Edit project pom.xml to enable updating the Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. *To-do*: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus *DONE* * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for new Nexus host (nexus.bioviz.org) *DONE* * Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. The current Nexus repository used by the IGB project resides at eos.transvar.org/nexus and is using very out-of-date version of Sonatype Nexus software. *To-do*: * Set up a new Nexus repository on AWS in Docker container using the latest software from Nexus *DONE* * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for new Nexus host (nexus.bioviz.org) *DONE* * Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. 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 on AWS in Docker container using the latest software from Nexus *DONE* * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for new Nexus host (nexus.bioviz.org) *DONE* * Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. 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 on AWS in Docker container using the latest software from Nexus *DONE* * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for new Nexus host (nexus.bioviz.org) *DONE* * Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) |
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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. 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 on AWS in Docker container using the latest software from Nexus *DONE* * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for new Nexus host (nexus.bioviz.org) *DONE* * Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server with repositories to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) to enable easy replication of same if required |
Additional details are available in the Google drive folder: Nexus Maven Deployment IGB Artifacts
Relevant documents:
Explain How to Deploy IGB Artifacts to a Nexus Repository
Local nexus process - mac
Windows OS: Install, start, create repository and deploy to nexus.docx
nexus AWS setup
| Status | In Progress [ 3 ] | Pull Request Submitted [ 10101 ] |
| Assignee | Deepti Joshi [ djoshi4 ] | Ann Loraine [ aloraine ] |
| Status | Pull Request Submitted [ 10101 ] | Needs Testing [ 10002 ] |
| Assignee | Ann Loraine [ aloraine ] | Ivory Blakley [ ieclabau ] |
| 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. Previously, this may have been done by hand via the repository Web-based interface. (Developers did not document it.) Also, developers obtained jar files from other projects and transformed them into OSGi bundles, which is required for them to be used in IGB, which runs within an OSGi container. 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 on AWS in Docker container using the latest software from Nexus *DONE* * Edit and update Dockerfile in private (for now) Loraine lab Container repository in https://bitbucket.org/lorainelab/container (edit Nexus/Dockerfile) * Set up user-friendly address for new Nexus host (nexus.bioviz.org) *DONE* * Edit project pom.xml to enable updating IGB artifacts to Nexus repository using Sonatype plugin; develop a release procedure for newly created artifacts * Migrate legacy artifacts from previous repository to new one, including IGB artifacts, GenoViz SDK artifacts, and 3rd party artifacts converted to OSGi bundles by previous developers * Document all of the above in the IGB course module dealing with releases * Push docker image of fully-configured server with repositories to Docker Hub (https://hub.docker.com/r/lorainelab/nexus/) to enable easy replication of same if required |
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 |
| Comment |
[ Address of on-line maven repositories host
52.23.208.180 nexus.bioviz.org Docker hub location for fully configured Docker image https://hub.docker.com/r/lorainelab/nexus/ Note: each image should be versioned ] |
| Comment | [ Test by making sure you can build the project. ] |
| Status | Needs Testing [ 10002 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Needs Testing [ 10002 ] |
| Assignee | Ivory Blakley [ ieclabau ] | Ann Loraine [ aloraine ] |
| Status | Needs Testing [ 10002 ] | In Progress [ 3 ] |
| Fix Version/s | 9.0.1 Minor Release [ 10500 ] |
| Fix Version/s | 9.0.1 Minor Release [ 10500 ] |
| Resolution | Done [ 10000 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 17894 ] | Fall 2019 Workflow Update [ 19837 ] |
| Workflow | Fall 2019 Workflow Update [ 19837 ] | Revised Fall 2019 Workflow Update [ 21956 ] |
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