Uploaded image for project: 'Build'
  1. Build
  2. BUILD-699

Configure Nexus 3' staging repositories

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Neutral
    • None
    • None
    • None
    • None

    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

        Acceptance criteria

        Attachments

          Activity

            People

              mmichel Maxime Michel
              mmichel Maxime Michel
              Foundation
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR