Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • 3.0.0
    • Blobstore, Replication
    • None

    Description

      When a user installs Nexus Repository to more than one location, there is often a need to efficiently transfer the private components between instances such that the teams located in other locations can access the newly created or updated components as efficiently as possible. Proxying is one way to get the components across the instances, however, proxying is on-demand and components requested are transferred only after they are requested. If the components are large in size, or the network bandwidth between the instances is slow, the time taken to successfully respond to the request may be too long for some automated processes and can cause intermittent timeout issues.

      This improvement aims to address the following scenarios:

      • Proactively transfer of components between Nexus Repository instances

      This improvement does not address the following scenarios:

      • Transfer of Nexus Repository configuration settingsĀ 
      • Transfer of User/Security settings

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              klau Kam-Wai Lau [X] (Inactive)
              Hardeep Nagra Hardeep Nagra
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                tigCommentSecurity.panel-title