Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-117

Replacing rsync with a direct use of Nexus API calls and reorganize the current repositories

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • Q4FY20
    • None
    • None
    • None
    • Replacing rsync with a direct use of Nexus API calls
    • Done
    • FY20-O2.3 Process Improvements
    • 0% To Do, 0% In Progress, 100% Done

      The old system of using rsync caused a lot of complications especially due to duplicates in the repositories. No we need to change the way how it is done.

      1) Old product repositories will be merged together into a newly created repository(ies) and duplicates will be taken care of.
      2) For each product a new staging profile will be created so they can be used to deploy the artifacts
      3) Promotion profiles for each product, that will promote the deployed staging repositories for testers
      4) Internal group repositories for testers (they will look like product-all, product-ea, product-techpreview, but will contain not yet released artifacts, but promoted by 3)
      5) Promotion profiles for official releases

      Test group repositories will be accessible for people with product-tester role and all above will be accessible and manageable by people in product-deployer security group.

              dhladky@redhat.com David Hladky
              cobrien@redhat.com Christopher O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: