Details
-
Task
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
This is the last blocker on our way to the migration. Unfortunately, staging has changed quite a bit. Nevertheless, do it using the following instance: https://nexus3.magnolia-cms.com
magnolia-mgmt being the main user of Nexus 2 staging repositories, it should be rewritten in order to use the following Maven plugin rather than the staging profile: https://help.sonatype.com/integrations/nexus-and-continuous-integration/repository-manager-for-maven-plugin
Notes
The poms hold a bunch of settings that are meant so that any community or enterprise user may use our staging repositories. With Nexus 3's rewrite it looks like we wouldn't even be able to migrate those use cases. Indeed, the possibilities offered by Nexus 3 are more minimalistic. Shouldn't we start from a blank page and let the Foundation team's tooling handle staging in 100% of cases? Yes, there is no other choice.
Checklists
Attachments
1.
|
Update Maven settings to include the Nexus 3 server |
|
Reopened | Unassigned |
2.
|
Basic configuration for Nexus 3 |
|
Closed | Maxime Michel |
3.
|
Make the release-job release to Nexus 3 on top of Nexus 2 |
|
Closed | Unassigned |
4.
|
Create a magnolia-mgmt console view to see currently staged artifacts |
|
To Do | Unassigned |
5.
|
Retire all Nexus 2 release & staging configuration from poms |
|
Closed | Unassigned |
6.
|
Check that the CLI and Docker images still can pull from Nexus 3 |
|
Closed | Unassigned |
7.
|
Create permanent staging repositories for public, enterprise, etc. |
|
Completed | Mikaël Geljić |