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

Repository Health Check is not identifying gems in rubygems proxy repository

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.13.0
    • Fix Version/s: None
    • Labels:
    • Notability:
      4

      Description

      Repository Health Check is not identifying gems in rubygems proxy repository.

      Steps to reproduce:

      1. create a new rubygems proxy repository
      2. gem install a few components eg aws-sdk and docker-api
      3. verify that the gem files are in the proxy by browsing the repository
      4. click Analyze to start repository Health Check
      5. when the scan completes, mouse over the "insufficient trend data" message to look at the report

      The results show that 0 components were identified.

      Expected the gem files in the repository to be identified.

      Download the gem files from the repository and scan them using the CLI. The components are identified in the report generated from the CLI scan.

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            cseney Cassandra Seney
            CC:
            Bob DeRosa, Erich Sanderford
            Last Updated By:
            Joe Tom Joe Tom
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title