[JIRA] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure

[pransp...@gmail.com (JIRA)]

Title: Message Title

Patrick Ranspach commented on JENKINS-26481   Re: Mishandling of binary methods accepting Closure Can we add this to the epic: 2.0: Pipeline as Code? This seems very important to using Groovy in a pipeline as code. It can be easily reproduced and blocks dependable groovy functionality. Also relevant labels: 2.0, 2.0-planned, testfest, windows, workflow Maybe also related, I'm only able to access closure arguments within returned closures if I copy the argument: def test = { name -> def path = 'services/' + name return { _ -> println(name) // .. do something } } will print the same 'name' with this code: def options = []; ['test', 'test1', 'test2'].each { iter -> options << test(iter) } options.each {it()} return options In a Jenkins Pipeline I have to save the argument, like: def test = { arg -> def name = arg; def path = 'services/' + name return { _ -> println(name) // .. do something } } Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.