【问题标题】:Using nested command substitution in jenkins pipeline sh step在 jenkins 管道 sh 步骤中使用嵌套命令替换
【发布时间】:2019-02-28 06:04:54
【问题描述】:

我试图在归档之前使用指向相关内部文件夹的符号链接来展平结果目录,该链接首先遍历在运行时确定的一堆变量路径名。使用我从这个 SO answer 中选择的这种命令替换方法,我似乎无法正确理解语法。

问题:是否有关于如何从我不知道的 Jenkins 管道步骤中正确转义命令替换链的规则?

管道脚本 sn-p

post {
  always {   
    sh """
    echo 'Link to inner output result folder to make the artifacts more shallow'
    echo ln -sf dirname find $output_dir -name $jUnitResult $WORKSPACE/$output_dir_inner
    ln -sf $(dirname $(find ${output_dir} -name ${jUnitResult})) $WORKSPACE/$output_dir_inner
    """

    archiveArtifacts output_dir_inner
  }
}

控制台输出

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 52: illegal string body character after dollar sign;
   solution: either escape a literal dollar sign "\$5" or bracket the value expression "${5}" @ line 52, column 21.
               ln -sf $(dirname $(find ${output_dir} -name ${jUnitResult})) $WORKSPACE/$output_dir_inner
                       ^

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:139)
    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:131)
    at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125)
    at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560)
    at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521)
    at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330)
    at hudson.model.ResourceController.execute(ResourceController.java:97)
    at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE

我在尝试时看到类似的失败

管道脚本 sn-p

ln -sf $(dirname $(find $output_dir -name $jUnitResult)) $WORKSPACE/$output_dir_inner

控制台输出

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 49: illegal string body character after dollar sign;
   solution: either escape a literal dollar sign "\$5" or bracket the value expression "${5}" @ line 49, column 13.
               sh """
               ^

【问题讨论】:

    标签: jenkins sh jenkins-pipeline


    【解决方案1】:

    围绕这个问题的几个有趣的策略

    将长 sh 脚本分解为具有返回值的不同功能片段

    https://stackoverflow.com/a/47394132/1330381

    使用反斜杠 \$ 转义嵌套的 shell 命令,

    sh """
        \$(echo TEST this subshell \$(ls .))
    """
    

    https://stackoverflow.com/a/50356318/1330381

    【讨论】:

    • 我可能应该更认真地阅读失败消息solution: either escape a literal dollar sign "\$5";它就在你面前。知道“谁在说话”有点迷失方向,我想当我看到编译失败时,我认为这是一个 bash 错误,而不是 jenkins 解析错误。现在我了解了这种技术,我可以明确地将该错误消息解释为源自 Jenkins 而不是 bash。
    猜你喜欢
    • 1970-01-01
    • 2016-09-10
    • 2017-07-22
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2019-03-30
    • 2017-11-14
    • 2018-06-29
    相关资源
    最近更新 更多