使用带有闭包映射的 failFast 会破坏“并行".步 [英] Using failFast with closure map breaks "parallel" step
本文介绍了使用带有闭包映射的 failFast 会破坏“并行".步的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
不确定这是我对 Groovy 的有限了解还是 Pipeline parallel
步骤中的怪癖.如果我使用 map 而不是单独传递每个闭包,我无法让它接受 failFast
:
Not sure if it's my limited knowledge of Groovy or a quirk in Pipeline parallel
step. I can't make it accept failFast
if I use map instead of passing each closure individually:
def map = [:]
map['spam'] = {
node {
echo 'spam'
}
}
map['eggs'] = {
node {
echo 'eggs'
}
}
parallel map // Works.
parallel spam: map['spam'], eggs: map['eggs'], failFast: true // Works.
parallel map, failFast: true // Fails with exception.
failFast
的异常是:
java.lang.IllegalArgumentException: Expected named arguments but got [{failFast=true}, {spam=org.jenkinsci.plugins.workflow.cps.CpsClosure2@51a382ad, eggs=org.jenkinsci.plugins.workflow.cps.CpsClosure2@718cb50d}]
at org.jenkinsci.plugins.workflow.cps.DSL.parseArgs(DSL.java:276)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:111)
推荐答案
map.failFast = true
parallel map
这篇关于使用带有闭包映射的 failFast 会破坏“并行".步的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文