A patch to groovy-cps as in #2 would be the appropriate fix, I think. If we are entering certain overloads of GroovyShell.evaluate and we get a continuation from some Script.run implementation, then all is well and there should be no warning.
Thank you, I will prepare an implementation with tests for this case.
Ok, just prepared a couple of PR's:
Jesse Glick could you please check them?
I've merged the groovy-cps PR and will be cutting a release today.
The changes of PR#315 was merged to the master of workflow-cps-plugin - so hopefully will be available in the next release 2.75
A fix for this issue was just released in Pipeline: Groovy Plugin version 2.75.
Yep, confirmed here: https://github.com/griddynamics/mpl/issues/31#issuecomment-548919000