Jenkins流水线跨Stage访问变量报错及awk用法咨询
Jenkins流水线跨Stage变量访问编译错误修复
问题场景
尝试在Jenkins流水线不同Stage间传递变量:
- Stage 1生成包含
os_type的配置文件 - Stage 2通过
grep+awk解析文件并赋值给全局变量os_type - Stage 3输出变量值
原流水线代码:
def os_type pipeline { agent {label 'jenLab'} stage('stage 1') { steps { sh ''' echo "ver=1.3.0" > ${WORKSPACE}/some_file echo "os_type=win" > ${WORKSPACE}/some_file ''' } } stage('stage 2') { steps { script{ os_type = sh( script: "grep "os_type" ${WORKSPACE}/some_file | awk -F "=" '{print $2}'", returnStdout: true, ) } } } stage('stage 3') { steps { echo "From stage 1 : ${os_type}" } } }
报错信息
Running in Durability level: MAX_SURVIVABILITY org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 16: unexpected token: os_type @ line 16, column 22. script: "grep "os_type" ${WORKSPACE}/some_file | awk -F "=" '{print $2}'", ^ 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:150) at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:120) at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:132) at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:350) at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:144) at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:110) at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:234) at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:168) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:943) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:605) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:337) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) Finished: FAILURE
错误原因
- Groovy字符串引号冲突:双引号包裹的shell脚本中,嵌套双引号未转义,导致Groovy语法解析失败。
- 文件覆盖问题:Stage 1中使用
>写入文件会覆盖之前的ver=1.3.0行,最终文件仅保留os_type=win。 - Awk变量被Groovy解析:
awk中的$2在Groovy双引号字符串中会被当作Groovy变量解析,无法正确传递给shell。
修复后的代码
def os_type pipeline { agent {label 'jenLab'} stages { stage('stage 1') { steps { sh ''' echo "ver=1.3.0" > ${WORKSPACE}/some_file echo "os_type=win" >> ${WORKSPACE}/some_file ''' } } stage('stage 2') { steps { script{ // 用三重单引号包裹shell脚本,避免引号冲突,同时保留shell变量解析 os_type = sh( script: '''grep "os_type" ${WORKSPACE}/some_file | awk -F "=" '{print $2}' ''', returnStdout: true, ).trim() // 去除输出中的换行符 } } } stage('stage 3') { steps { echo "From stage 1 : ${os_type}" } } } }
关键调整说明
- 引号处理:用三重单引号(
''')包裹shell脚本,Groovy不会解析单引号内的内容,避免双引号嵌套冲突,同时${WORKSPACE}仍能被shell正确解析。 - 文件写入方式:将Stage 1中的第二个
>改为>>,实现内容追加,保留两行配置。 - 去除换行符:添加
.trim()方法,去掉sh返回结果中的换行符,避免输出时出现多余空行。 - 规范语法:补充
stages块,符合Jenkins流水线的标准写法。
内容的提问来源于stack exchange,提问作者vinWin
相关产品推荐
相关产品推荐

