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

programatically creating a repository using REST or Groovy scripting, does not enable repository health check

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not A Bug
    • Affects Version/s: 3.24.0
    • Fix Version/s: None
    • Labels:

      Description

      1. Enable repository health check(RHC) on all proxy repos.
      2. Create a new proxy repository using either the REST API ( POST /beta/repositories/(format)/proxy ) or using Groovy Scripting ( example RepositoryApi.createMavenProxy() ). Add content to the repository.
      3. Now go to the repositories list and hover your cursor over the Health check column. There will be a popup that says:

        Repository Health Check Unavailable

      A Repository Health Check (RHC) cannot be performed on this repository, because it is an unsupported type or out of service.

      How the IQ Server Repository Health Check can help you make better software faster

      But, the repository is of a supported type ( maven) and the repository is not out of service. There appears to be no easy way to get a repository out of this broken health check state.

      However, if you create a repository using the UI, then hover over the Health check column, you will see that the repository health check feature works.

      Expected

      Creating proxy repositories using REST API when healthcheck is enabled for all repositories should act the same way as when a repository is created using UI.

       

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title