|
|
|
|
|
|
by vorg
3361 days ago
|
|
|
> using groovy collections methods is veyr inconvinient It looks like Blue Ocean generates Apache Groovy DSL code for the pipeline. From their pipeline doco [1]: _In order to provide durability, which means that running Pipelines can survive a restart of the Jenkins master, Scripted Pipeline must serialize data back to the master. Due to this design requirement, some Groovy idioms such as collection.each { item -> /* perform operation */ } are not fully supported_ I wonder how feasible it is to make any edits at all to the DSL and have the new code read in successfully by the Blue Ocean UX. Perhaps the collections methods aren't the only restrictions. [1] https://jenkins.io/doc/book/pipeline/syntax/#differences-fro... |
|
|