在shell中生成的并行管道中访问Groovy变量

我一直在Jenkins管道中访问shell步骤中的groovy变量

我读书，但不能得到我想要的工作预期

这是我的管道：

//虽然当前不能使用Groovy的.collect或类似方法，但可以
//仍然将列表转换为要在中执行的一组实际构建步骤
//平行。
//我们希望并行回显的字符串的初始列表
def templast=dusboard.split（'，）.collect{it as String}
def stringsToEcho=[“a”、“b”、“c”、“d”]
//在执行并行步骤之前，我们将在其中存储并行步骤的映射。
def stepsForParallel=templast.collectEntries{
[“echoing${it}”：transformIntoStep（it）]
}
//实际上并行运行这些步骤-并行将映射作为参数，
//因此，上述情况。
平行阶梯
//拿着绳子，回音。
def转换步骤（tmpBoard）{
//我们需要将返回的内容封装在Groovy闭包中，否则它将被调用
//当调用此方法时，而不是当我们将其传递给并行程序时。
//为此，需要将下面的代码包装在{}中，然后返回
//这是显式的，或者使用{->}语法。
返回{
节点（'tb-tftp-server'）{
回音tmpBoard
阶段（'安装'）{
env.board=tmpBoard
锁（资源：$tmpBoard）{
“嘘”
hwjs=“hw-\${board}.js”
回声“1$hwjs”
hwjs=“hw-\${tmpBoard}.js”
echo“2$hwjs”
'''
}
锁（资源：$tmpBoard）{
“嘘”
回显''+tmpBoard+'abcd''
'''
}
}
}
}
}

如果我使用dus011、dus012作为输入参数执行它（即变量dusboard=dus011、dus012），则输出如下

[echoing dus011] Trying to acquire lock on [dus011]
[echoing dus011] Lock acquired on [dus011]
[Pipeline] [echoing dus011] {
[Pipeline] [echoing dus012] lock
[echoing dus012] Trying to acquire lock on [dus012]
[echoing dus012] Lock acquired on [dus012]
[Pipeline] [echoing dus012] {
[Pipeline] [echoing dus011] sh
[echoing dus011] [lionel_test3] Running shell script
[echoing dus011] + hwjs=hw-dus012.js
[echoing dus011] + echo '1 hw-dus012.js'
[echoing dus011] 1 hw-dus012.js
[echoing dus011] + hwjs=hw-.js
[echoing dus011] + echo '2 hw-.js'
[echoing dus011] 2 hw-.js
[Pipeline] [echoing dus012] sh
[echoing dus012] [lionel_test3@2] Running shell script
[Pipeline] [echoing dus011] }
[echoing dus011] Lock released on resource [dus011]
[Pipeline] [echoing dus011] // lock
[echoing dus012] + hwjs=hw-dus012.js
[echoing dus012] + echo '1 hw-dus012.js'
[echoing dus012] 1 hw-dus012.js
[echoing dus012] + hwjs=hw-.js
[echoing dus012] + echo '2 hw-.js'
[echoing dus012] 2 hw-.js
[Pipeline] [echoing dus011] lock
[echoing dus011] Trying to acquire lock on [dus011]
[echoing dus011] Lock acquired on [dus011]
[Pipeline] [echoing dus011] {
[Pipeline] [echoing dus011] sh
[echoing dus011] [lionel_test3] Running shell script
[Pipeline] [echoing dus012] }
[echoing dus012] Lock released on resource [dus012]
[Pipeline] [echoing dus012] // lock
[echoing dus011] + echo dus011 abcd
[echoing dus011] dus011 abcd
[Pipeline] [echoing dus012] lock
[echoing dus012] Trying to acquire lock on [dus012]
[echoing dus012] Lock acquired on [dus012]
[Pipeline] [echoing dus012] {
[Pipeline] [echoing dus012] sh
[echoing dus012] [lionel_test3@2] Running shell script
[Pipeline] [echoing dus011] }
[echoing dus011] Lock released on resource [dus011]
[Pipeline] [echoing dus011] // lock
[Pipeline] [echoing dus011] }
[echoing dus012] + echo dus012 abcd
[echoing dus012] dus012 abcd
[Pipeline] [echoing dus011] // stage
[Pipeline] [echoing dus011] }
[Pipeline] [echoing dus011] // node
[Pipeline] [echoing dus011] }
[echoing dus011] Failed in branch echoing dus011
[Pipeline] [echoing dus012] }
[echoing dus012] Lock released on resource [dus012]
[Pipeline] [echoing dus012] // lock
[Pipeline] [echoing dus012] }
[Pipeline] [echoing dus012] // stage
[Pipeline] [echoing dus012] }
[Pipeline] [echoing dus012] // node
[Pipeline] [echoing dus012] }
[echoing dus012] Failed in branch echoing dus012
[Pipeline] // parallel
[Pipeline] End of Pipeline
Also:   java.lang.NullPointerException: Cannot get property '
             ' on null object
java.lang.NullPointerException: Cannot get property '
             ' on null object

我们可以看到lock命令具有正确的板：一次是dus011，另一次是dus012=>良好

但是这个是错误的，应该是hw-dus011.js，而不是hw-dus012.js。我认为这是因为它是一个环境变量，第二个//阶段覆盖了第一个==>糟糕

电路板名称的其他打印错误

所以我试着使用了''+'语法。听起来不错，因为这一次板名与[echoing dus011]dus011 abcd和[echoing dus012]dus012 abcd匹配，但Java异常：（

我的错误在哪里？如何解决

---

感谢您的帮助

我相信这可能会发生，因为在并行块中，您正在通过执行

env.board=tmpBoard

修改全局

env

变量。这些块之间存在基于写/读访问的竞争条件

我认为最好的方法是在块内部使用

withEnv

，以隔离设置环境的上下文

而不是

env.board=tmpBoard

你可以

withEnv（[“board=$tmpBoard”]）{
//需要板作为环境变量的代码块
}

除了我用env（[“board=$tmpBoard”]）将tmpBoard扩展到board中的事实之外，它起作用了。谢谢你的精彩捕捉，谢谢你指出@Lionelon。编辑了答案。