Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63264

Docker Pipeline: Hardcoded requirement to prefix registry with https:// doesn't work with Nexus

XMLWordPrintable

      When creating a Multibranch Pipeline job (or globally in Jenkins configuration), it is possible to specify an alternate Docker registry to pull images from. Unfortunately, the input field considers URLs w/o "https://" prefix as invalid, which is wrong if the registry is hosted on a Sonatype Nexus repository server or in AWS ECR. In this case the registry must be provided as either <hostname>:<port> (Nexus) or just <hostname> (AWS ECR), but this is not accepted.

      However, it's working fine when using Docker commands directly, for example:

      docker login <hostname>:<port>

      or

      docker push <hostname>:<port>/<image>:<tag>

      Please fix the plugin so that it works with above Docker registries.

          [JENKINS-63264] Docker Pipeline: Hardcoded requirement to prefix registry with https:// doesn't work with Nexus

          Dirk Heinrichs created issue -
          Dirk Heinrichs made changes -
          Description Original: When creating a Multibranch Pipeline job (or globally in Jenkins configuration, it is possible to specify an alternate Docker registry to pull images from. Unfortunately, the input field considers URLs w/o "https://" prefix as invalid, which is wrong if the registry is hosted on a Sonatype Nexus repository server or in AWS ECR. In this case the registry must be provided as either <hostname>:<port> (Nexus) or just <hostname> (AWS ECR), but this is not accepted.

          However, it's working fine when using Docker commands directly, for example:
          {code:java}
          docker login <hostname>:<port>{code}
          or
          {code:java}
          docker push <hostname>:<port>/<image>:<tag>{code}
          Please fix the plugin so that it works with above Docker registries.           		New: When creating a Multibranch Pipeline job (or globally in Jenkins configuration), it is possible to specify an alternate Docker registry to pull images from. Unfortunately, the input field considers URLs w/o "https://" prefix as invalid, which is wrong if the registry is hosted on a Sonatype Nexus repository server or in AWS ECR. In this case the registry must be provided as either <hostname>:<port> (Nexus) or just <hostname> (AWS ECR), but this is not accepted.

          However, it's working fine when using Docker commands directly, for example:
          {code:java}
          docker login <hostname>:<port>{code}
          or
          {code:java}
          docker push <hostname>:<port>/<image>:<tag>{code}
          Please fix the plugin so that it works with above Docker registries.
          Dirk Heinrichs made changes -
          Summary Original: Docker Pipeline: Hardcoded requirements to prefix registry with https:// doesn't work with Nexus New: Docker Pipeline: Hardcoded requirement to prefix registry with https:// doesn't work with Nexus

          Dirk Heinrichs added a comment -

          Hello, anybody out there?

          Dirk Heinrichs added a comment - Hello, anybody out there?

          Dirk Heinrichs added a comment -

          Knock, knock...

          Dirk Heinrichs added a comment - Knock, knock...

            Unassigned Unassigned
            dhs Dirk Heinrichs
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: