Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58620

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


    • workflow-cps 2.75

      We found a change that prints an annoying warning about the CPS mismatch during running the MPL module: https://github.com/griddynamics/mpl/issues/31

      Running on Jenkins in /var/jenkins_home/workspace/mpl-master
      [Pipeline] {
      [Pipeline] stage
      [Pipeline] { (Checkout)
      [Pipeline] fileExists
      expected to call org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.evaluate but wound up catching Checkout.run; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/

      We're not quite sure how to fix that in the library, but realized that the issue is related to the change JENKINS-31314 introduced in workflow-cps-2.71.

      Reproduce is quite simple - just need to install the minimal latest jenkins, add required git & shared lib plugins, attach mpl library from github and create a simple jenkins job to build the mpl. It will fail (no Maven 3 tool) - but will show the issue during each module start.

      Who could help with determining the actual cause and how to fix that?

            sparshev Sergei Parshev
            sparshev Sergei Parshev
            0 Vote for this issue
            5 Start watching this issue