[JIRA] (JENKINS-58620) expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-58620 expected to call CpsGroovyShell.evaluate but wound up catching <something>.run Change By: Jesse Glick Summary: MPL shared library logic execution caused CPS mismatch warning expected to call CpsGroovyShell.evaluate but wound up catching <something>.run Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-58620

Re: expected to call CpsGroovyShell.evaluate but wound up catching <something>.run 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.

Add Comment

[sparshev@griddynamics.com (JIRA)]

Sergei Parshev commented on JENKINS-58620

Re: expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

Thank you, I will prepare an implementation with tests for this case.

Add Comment

[sparshev@griddynamics.com (JIRA)]

Sergei Parshev commented on JENKINS-58620

Re: expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

Ok, just prepared a couple of PR's: https://github.com/cloudbees/groovy-cps/pull/101 - with the exception implementation https://github.com/jenkinsci/workflow-cps-plugin/pull/315 - with the test of the minimal Jenkinsfile Jesse Glick could you please check them?

Add Comment

[andrew.bayer@gmail.com (JIRA)]

Andrew Bayer commented on JENKINS-58620

Re: expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

I've merged the groovy-cps PR and will be cutting a release today.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[sparshev@griddynamics.com (JIRA)]

Sergei Parshev commented on JENKINS-58620

Re: expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

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

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum resolved as Fixed

A fix for this issue was just released in Pipeline: Groovy Plugin version 2.75.

Jenkins / JENKINS-58620

expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: workflow-cps 2.75

Add Comment

[sparshev@griddynamics.com (JIRA)]

Sergei Parshev commented on JENKINS-58620

Re: expected to call CpsGroovyShell.evaluate but wound up catching <something>.run Yep, confirmed here: https://github.com/griddynamics/mpl/issues/31#issuecomment-548919000

Add Comment

[sparshev@griddynamics.com (JIRA)]

Sergei Parshev closed an issue as Fixed

Jenkins / JENKINS-58620

expected to call CpsGroovyShell.evaluate but wound up catching <something>.run

Change By: Sergei Parshev Status: Resolved Closed

Add Comment