Jenkins pipeline语法：声明式语法和Script语法

Started by user admin[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/parameters[Pipeline] {[Pipeline] stage[Pipeline] { (stage1)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipeline//报错没有这样的属性或类Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 455f3d00-5cdd-4aef-944f-432240771accgroovy.lang.MissingPropertyException: No such property: name for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:285) at org.kohsuke.groovy.sandbox.impl.Checker$7.call(Checker.java:375) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:379) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:355) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:355) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29) at org.jenkinsci.plugins.workflow.cps.LoggingInvoker.getProperty(LoggingInvoker.java:121) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:10) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(ModelInterpreter.groovy:137) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(ModelInterpreter.groovy:666) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(ModelInterpreter.groovy:395) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(ModelInterpreter.groovy:393) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(ModelInterpreter.groovy:665) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:288) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.toolsBlock(ModelInterpreter.groovy:544) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.toolsBlock(ModelInterpreter.groovy:543) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:276) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:443) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:442) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:275) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withCredentialsBlock(ModelInterpreter.groovy:481) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withCredentialsBlock(ModelInterpreter.groovy:480) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:274) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inDeclarativeAgent(ModelInterpreter.groovy:586) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inDeclarativeAgent(ModelInterpreter.groovy:585) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:272) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.stageInput(ModelInterpreter.groovy:356) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.stageInput(ModelInterpreter.groovy:355) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:261) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inWrappers(ModelInterpreter.groovy:618) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inWrappers(ModelInterpreter.groovy:617) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:259) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:443) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:442) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage(ModelInterpreter.groovy:254) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:73) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:65) at jdk.internal.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) 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:152) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:146) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:136) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:275) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:146) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:187) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:423) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:331) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:295) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:97) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:139) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68) at jenkins.util.ErrorLoggingExecutorService.lambda$wrap$0(ErrorLoggingExecutorService.java:51) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)Finished: FAILURE

第二次构建

日志输出

Started by user admin[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/parameters[Pipeline] {[Pipeline] stage[Pipeline] { (stage1)[Pipeline] echoliangxi[Pipeline] echotrue[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS

Started by user admin[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/parameters[Pipeline] {[Pipeline] stage[Pipeline] { (stage1)[Pipeline] echo你好[Pipeline] echofalse[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS

triggers 指令定义了 Pipeline 自动化触发的方式。目前有三个可用的触发器：cron 和 pollSCM 和upstream作用域：被pipeline包裹，在符合条件下自动触发pipeline1、cron：接受一个 cron 风格的字符串来定义 Pipeline 触发的时间间隔，例如：triggers { cron('H 4/* 0 0 1-5') }cron 表达式的各个字段：H：代表 Hashed 值，用于避免多个任务同时触发。在每个小时内，相同的 H 值只会触发一个任务。这可以确保任务在指定的时间范围内只执行一次。4/*：表示分钟字段，指定每小时的第 4 分钟。0：表示小时字段，指定小时为 0 点。0：表示天字段，指定日期为任意日期。1-5：表示工作日字段，指定工作日为周一到周五。综上所述，该 cron 触发器的定义规则意味着在每个工作日的凌晨 0 点 4 分触发 Pipeline 的执行。这意味着 Pipeline 会在工作日的每个早晨 0 点 4 分执行一次。

stage 的 input 指令允许你使用 input step 提示输入。 在应用了 options 后，进入 stage 的agent 或评估 when 条件前，stage 将暂停。 如果 input 被批准, stage 将会继续。 作为 input 提交的一部分的任何参数都将在环境中用于其他 stage配置项message必需的。 这将在用户提交 input 时呈现给用户。idinput 的可选标识符， 默认为 stage 名称。ok`input`表单上的"ok" 按钮的可选文本。submitter可选的以逗号分隔的用户列表或允许提交 input 的外部组名。默认允许任何用户。submitterParameter环境变量的可选名称。如果存在，用 submitter 名称设置。parameters提示提交者提供的一个可选的参数列表。

pipeline { agent any stages { stage('Example') { input { message "Should we continue?" ok "Yes, we should." submitter "liangxi,lucky" parameters { string(name: 'PERSON', defaultValue: 'liangxi', description: 'Who should I say hello to?') } } steps { echo "Hello, ${PERSON}, nice to meet you." } } }}

Started by user admin[Pipeline] Start of Pipeline (hide)[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/input[Pipeline] {[Pipeline] stage[Pipeline] { (Example)[Pipeline] inputInput requestedApproved by admin[Pipeline] withEnv[Pipeline] {[Pipeline] echoHello, liangxi, nice to meet you.[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS

Declarative Pipeline 近期新增了对并行嵌套 stage 的支持，对耗时长，相互不存在依赖的 stage可以使用此方式提升运行效率。除了 parallel stage，单个 parallel 里的多个 step 也可以使用并行的方式运行是否并行构建

pipeline{ agent any stages{ stage('Non-parallel Stage'){ steps{ echo 'This stage will be executed first' } } stage('Parallel Stage'){ when{ branch 'master' } parallel{ stage('branch A'){ agent{ label"for-branch-a" } steps{ echo "On Branch A" } } stage('Branch B'){ agent{ label "for-branch-b" } steps{ echo "On Branch B" } } } } }}

Started by user admin[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/Parallel[Pipeline] {[Pipeline] stage[Pipeline] { (Non-parallel Stage)[Pipeline] echoThis stage will be executed first[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Parallel Stage)Stage "Parallel Stage" skipped due to when conditional[Pipeline] parallel[Pipeline] { (Branch: branch A)[Pipeline] { (Branch: Branch B)[Pipeline] stage[Pipeline] { (branch A)[Pipeline] stage[Pipeline] { (Branch B)Stage "branch A" skipped due to when conditional[Pipeline] }Stage "Branch B" skipped due to when conditional[Pipeline] }[Pipeline] // stage[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS

script Pipeline 提供了一组预定义的指令和块，使得构建、测试、部署等常见任务的编写变得更加容易。这种语法风格非常适合于简单到中等复杂度的流水线，并且可读性较高。它的主要优点是易于上手、易于理解和维护，并且具有一定的安全性，可以限制流水线的操作范围。选择 Declarative Pipeline 还是 Scripted Pipeline 取决于你的具体需求。如果你的流水线相对简单，且易于使用和理解，则 Declarative Pipeline 是一个不错的选择。如果你需要更高级的功能和更大的灵活性，或者需要与外部系统进行复杂的交互，则 Scripted Pipeline 可能更适合你的需求。

node('testhan') { #testhan为以上设置的Pod模板标签 stage('Clone') { echo "1.Clone Stage" #第一步克隆代码 git url: "https://gitee.com/howehonkei/jenkins-sample" #gitee地址 script { build_tag = sh(returnStdout: true, script: 'git rev-parse --short HEAD').trim() } } stage('Test') { echo "2.Test Stage" #打印2.Test Stage
 } stage('Build') { #构建镜像 echo "3.Build Docker Image Stage" sh "docker build -t 192.168.1.130/jenkins-demo/jenkins-demo:${build_tag} ." #构建后的名字：仓库地址/项目名/镜像名:版本号 } stage('Push') { #上传到镜像仓库 echo "4.Push Docker Image Stage" withCredentials([usernamePassword(credentialsId: 'dockerharbor',passwordVariable: 'dockerHubPassword', usernameVariable: 'dockerHubUser')]) { sh "docker login 192.168.1.130 -u ${dockerHubUser} -p ${dockerHubPassword}" sh "docker push 192.168.1.130/jenkins-demo/jenkins-demo:${build_tag}" } } stage('Deploy to dev') { echo "5. Deploy DEV" sh "sed -i 's//${build_tag}/' k8s-dev-harbor.yaml " sh "kubectl apply -f k8s-dev-harbor.yaml --validate=false" }  stage('Promote to qa') {  def userInput = input( id: 'userInput',
 message: 'Promote to qa?', #是否部署到qatest测试环境 parameters: [ [ $class: 'ChoiceParameterDefinition', choices: "YESnNO", name: 'Env' ] ] ) echo "This is a deploy step to ${userInput}" if (userInput == "YES") { #如果是则部署，如果不是则exit退出 sh "sed -i 's//${build_tag}/' k8s-qa-harbor.yaml " sh "kubectl apply -f k8s-qa-harbor.yaml --validate=false" sh "sleep 6" sh "kubectl get pods -n qatest" } else { //exit } } stage('Promote to pro') {  def userInput = input(
 id: 'userInput', message: 'Promote to pro?', #是否部署到pro生产环境，如果是则部署，如果不是，则退出 parameters: [ [ $class: 'ChoiceParameterDefinition', choices: "YESnNO", name: 'Env' ] ] ) echo "This is a deploy step to ${userInput}" if (userInput == "YES") { sh "sed -i 's//${build_tag}/' k8s-prod-harbor.yaml " sh "kubectl apply -f k8s-prod-harbor.yaml --record --validate=false" } }}

pipeline{ agent{ node{ label 'testhan' } } stages{ stage('Clone'){ steps{ echo "1.Clone Stage" git url: "https://gitee.com/howehonkei/jenkins-sample" script{ build_tag=sh(returnStdout: true, script: 'git rev-parse --short HEAD').trim()) } } } stage('Test'){ steps{ echo "2.Test Stage" } } stage('Build'){ steps{ echo "3.Build Docker Image Stage" sh "docker build -t xuegod/jenkins-demo:${build_tag}" } } stage('Push'){ steps{ echo "4.Push Docker Image Stage" withCredentials([usernamePassword(credentialsId: 'dockerharbor',passwordVariable: 'dockerHubPassword', usernameVariable: 'dockerHubUser')]) { sh "docker login 192.168.1.130 -u ${dockerHubUser} -p ${dockerHubPassword}" sh "docker push 192.168.1.130/jenkins-demo/jenkins-demo:${build_tag}" } } } stage('Deploy to dev'){ steps{ echo "5. Deploy DEV" sh "sed -i 's//${build_tag}/' k8s-dev-harbor.yaml " sh "kubectl apply -f k8s-dev-harbor.yaml --validate=false" } } stage('Promote to qa') { steps{ def userInput = input( id: 'userInput', message: 'Promote to qa?', #是否部署到qatest测试环境 parameters: [ choice( choices: "YESnNO" description: 'Select an option' name: 'ENV' ) ] ) echo "This is a deploy step to ${userInput}" when { expression{ userInput == 'YES' } } steps{ sh "sed -i 's//${build_tag}/' k8s-qa-harbor.yaml " sh "kubectl apply -f k8s-qa-harbor.yaml --validate=false" sh "sleep 6" sh "kubectl get pods -n qatest" } } } stage("Promote to pro"){ steps{ def userInput = input( id: 'userInput', message: 'Promote to pro?', #是否部署到pro生产环境，如果是则部署，如果不是，则退出 parameters: [ choice( description: 'select an option' choices: "YESnNO", name: 'Env' ) ] ) echo "This is a deploy step to ${userInput}" when{ expression{ userInput == 'YES' } } steps{ sh "sed -i 's//${build_tag}/' k8s-prod-harbor.yaml " sh "kubectl apply -f k8s-prod-harbor.yaml --record --validate=false" } } } }}