Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-6644

check being released staging repos for component uniqueness on release

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: 2.6.4, 2.7.2, 2.8.1
    • Fix Version/s: None
    • Component/s: Staging
    • Labels:

      Description

      Given a target repository policy of Allow redeployments = false
      And 2 staging repos containing the same GAV x
      And target repository does not yet contain GAV x
      When the 2 staging repos are selected to release as part of a single bulk operation
      And the 2 staging repos are released
      Then the target repo should be checked for duplicates
      And the 2 'being released' staging repos should be checked for duplicate GAVs
      And the release should FAIL

      Actual: the release does not fail, since the default ruleset on release, only checks the target deployment policy and not the being released staging repos for duplicates.

      Adding an artifact uniqueness rule does not help either, since that rule currently relies on an up to date index, and the index may not be populated by the time the sha1 is searched for on release ( it is still being indexed asynchronously )

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title