Jenkins 聲明式管道 - 將 Docker 映像推送到私有 docker hub 存儲庫

Question

我嘗試從 Jenkins 推送到一個私有的 dockerhub 存儲庫，但我猜我總是因為授權而出錯。

這是相關的 Jenkins 管道：

pipeline {
  agent {
    // run this pipeline inside an docker image with node 8 and git installed
    docker {
      image 'node/8-alpine'
      registryUrl 'https://registry.hub.docker.com'
      registryCredentialsId 'dockerhub' // the id of username/password credentials I have in Jenkins
    }
  }
  environment {
    registry = '<my-org>/<my-project>'
    tag_beta = "${currentBuild.displayName}-${env.BRANCH_NAME}"
  }
  stages {

    stage("Docker") {
      steps {
          script {
            // NPM_TOKEN was set as environment variable inside Jenkins
            def image = docker.build("${env.registry}:${env.tag-beta}",  "-e NPM_TOKEN=${env.NPM_TOKEN}")
            /* Push the container to the custom Registry */
            image.push()
          }

      }
    }
  }
}

這是錯誤堆棧跟蹤

groovy.lang.MissingPropertyException: No such property: beta for class: groovy.lang.Binding
    at groovy.lang.Binding.getVariable(Binding.java:63)
    at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264)
    at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:289)
    at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:293)
    at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:269)
    at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:269)
    at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:269)
    at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:269)
    at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29)
    at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
    at WorkflowScript.run(WorkflowScript:57)
    at ___cps.transform___(Native Method)
    at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
    at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
    at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
    at sun.reflect.GeneratedMethodAccessor351.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
    at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
    at com.cloudbees.groovy.cps.Next.step(Next.java:83)
    at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
    at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
    at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
    at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
    at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)
    at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)
    at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:182)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)
    at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
    at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
    at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE

我也試過

docker.withRegistry('', "myJenkinsCredentialsIdForDockerhub") {            
  /* Push the container to the custom Registry */
  image.push()
}

任何有關如何從 Jenkins 聲明性管道到私有 Docker 集線器注冊表進行身份驗證的幫助將不勝感激！

Answer 1

在這里，我如何創建帶有兩個標簽的圖像，將其推送到私有存儲庫並從本地刪除圖像：

stage('Build and Push Docker Images'){
    steps{
        script {
            def imageName = "${containerRegistry}/${serviceName}/${optionalImageName}"
            docker.withRegistry("https://${containerRegistry}/${serviceName}", "1feb1e1e-9999-41bb-a269-89c999999999") {
                def customImage = docker.build(imageName)
                customImage.push("${newVersion}")
                customImage.push("latest")
                sh "docker rmi --force \$(docker images -q ${customImage.id} | uniq)"
            }
        }
    }
}

Answer 2

我想你有一個錯字：

def image = docker.build("${env.registry}:${env.tag-beta}",  "-e NPM_TOKEN=${env.NPM_TOKEN}"
                                                   ^

應該

def image = docker.build("${env.registry}:${env.tag_beta}",  "-e NPM_TOKEN=${env.NPM_TOKEN}"
                                                   ^

注意${env.tag_beta}的_ over -

Answer 3

withRegistry 需要將注冊表作為第一個參數，將憑據 ID（對於 jenkins 憑據）作為第二個參數。 工作示例方法：

/**
 * Stage **Push to registry**
 * login to Docker registry
 * @param dockerRegistryURL
 * @param dockerRegistryCredentialsId - Jenkins stored credentials for Docker registry
 * @param pushLatest - if true will push again with tag latest
 * @param newImage - Docker image handle with freshly built image to be pushed
 */
void push(String dockerRegistryURL, String dockerRegistryCredentialsId, boolean pushLatest, newImage) {
    stage('Push to registry') {
        echo (
            "pushing to registry url: 'https://${dockerRegistryURL}' " +
            "with credentials: '${dockerRegistryCredentialsId}'"
        )
        docker.withRegistry("https://${dockerRegistryURL}", dockerRegistryCredentialsId) {
            newImage.push()
            if (pushLatest)
                newImage.push("latest")
        }
    }
}

Answer 4

在這篇文章中有一個很好的解決方案，它對我有用： https : //issues.jenkins-ci.org/browse/JENKINS-48437?focusedCommentId=338354&page=com.atlassian.jira.plugin.system.issuetabpanels : comment- tabpanel#comment-338354

node {
    withDockerRegistry([credentialsId: 'docker-creds', url: 'https://index.docker.io/v1/']) {
        echo "Hello"
    }
}