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

No warning when using an non-existant credentials in withRegistry

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When trying to push a Docker image, it is possible to provide an non-existant credentialsId to withRegistry. However, there is no warning in the Pipeline script definition, only at runtime. And Docker says that authentication is required when in fact it is just because the provided credentials doesn't exist on the instance.

        Attachments

          Activity

          Hide
          jglick Jesse Glick added a comment -

          there is no warning in the Pipeline script definition, only at runtime

          Not sure where you were expecting a non-runtime warning to appear, exactly, without solving the Halting Problem.

          If there is a runtime warning, of course it ought to say that the credentials are invalid if they were supplied, but any failure to do so is likely a bug in the Docker client, not this plugin.

          Show
          jglick Jesse Glick added a comment - there is no warning in the Pipeline script definition, only at runtime Not sure where you were expecting a non-runtime warning to appear, exactly, without solving the Halting Problem. If there is a runtime warning, of course it ought to say that the credentials are invalid if they were supplied, but any failure to do so is likely a bug in the Docker client, not this plugin.

            People

            Assignee:
            jglick Jesse Glick
            Reporter:
            alecharp Adrien Lecharpentier
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: