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

Hide credentials given to the dockerfile

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When using jenkins with docker plugin, If I try to launch a dockerfile from pipeline with credentials as AdditionalArguments:

      def BUILDARGS
      node {
           withCredentials([usernamePassword(credentialsId: 'credId', passwordVariable: 'nexusPassword', usernameVariable: 'nexusUser')]) {
                BUILDARGS = "--build-arg nexusUser=${nexusUser} --build-arg nexusPassword=${nexusPassword}"
           }
      }
      agent {
           dockerfile {
               dir "${projectRootLocation}"
              additionalBuildArgs "$BUILDARGS"
               label 'Docker'
           }
      }

      Jenkins display the content of the command line :

      [Pipeline] sh
      [tform_xxxxxx_master-JY4H63NYHB6VJMKUFIMC2R2JWRWXIDSJ63WJCYILIZ35Y5AVGIUA] Running shell script
      
      docker build -t 5c5a6f87c431d14fd800e3cad7bb1d9af131caa4 --build-arg nexusUser=username --build-arg nexusPassword=password -f ./Dockerfile .
      Sending build context to Docker daemon 123.1MB

      So it possible to hide the password and the user on the command line ?

      Thanks

        Attachments

          Activity

          Hide
          stephenconnolly Stephen Connolly added a comment -

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Show
          stephenconnolly Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            20100 Vincent Guignot
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated: