I lost an afternoon to this bug and it's real and still open. The workaround mentioned of the split each works great. Just chiming in that this does actually need to be fixed.

Chiming in as well, having the same issue. Example:

	def tagged_branches = sh(returnStdout: true, script: "git branch --contains tags/${tag_name}")
	println tagged_branches
	tagged_branches.eachLine {
		println it
	}

Outputs:

12:36:41  + git branch --contains tags/v0.6.20
12:36:41  [Pipeline] echo
12:36:41    feature/install_from_net_drive
12:36:41  * master
12:36:41  
12:36:42  [Pipeline] echo
12:36:42    feature/install_from_net_drive
12:36:42  [Pipeline] }
12:36:42  [Pipeline] // script
12:36:42  [Pipeline] }

Just ran into this issue as well, but got this nice warning in the Jenkins output which helped me find the cause (i.e. this issue):

expected to call java.lang.String.eachLine but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/

node {
   def data = """# some useless text
                 |# even more
                 |finally interesting text"""
data.eachLine { String line ->
  println line
}

}

Same issue when we execute the above script.

expected to call java.lang.String.eachLine but wound up catching org.jenkinsci.plugins.workflow.cps.CpsClosure2.call; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/

Workaround is working really fine

As a workaround replace eachLine with split('\n').each { ... }

I don't feel that this issue is Minor, nor do I feel that the workaround is an acceptable solution. This basically means that every Jenkins user worldwide will burn some hours diagnosing this problem only to end up here.

That this bug is more than 2 years old speaks to a significant lack of care.

Likewise. Just burned a bit of time on this. Moving to the workaround.

I've just stumbled over this as well.

Same here.  What's worse is the error message links to a page https://jenkins.io/redirect/pipeline-cps-method-mismatches/ which has absolutely no hints on what the error could be, and assumes you know the internal workings of the groovy compiler.  No, I just want a simple and obvious construct to work..

Affects us as well

Also wasted time one this issue, but thanks to this bug report, quickly switched to workaround.

Confirming that this is still happening as of Jenkins 2.319.1.  I agree with tonyhoylerps that the CPS mismatch link is not helpful.

The Jenkins project recommends that these types of complex operations be performed with an sh step that calls the program of your choice. You can use groovy in that sh step or whatever other language you prefer. By placing the complex operation in an sh step, it can be executed on an agent instead of on the controller. By placing the complex operation in an sh step, it can use whatever language and version you prefer.

The Jenkins project recommends that these types of complex operations be performed with an sh step that calls the program of your choice.

Thank you for an utterly irrelevant copypasta response. The example shown is an sh step that calls the program of their choice, Mark. So your post just wasted everyone's time because it's not relevant or helpful in any way.

jorhett I don't think you understood the message that I was trying to convey.

The script provided in the bug description uses the Jenkins agent to perform an sh call to list the branches and uses the Jenkins agent to perform an sh call to list the containers. It then uses the Jenkins controller to iterate over the list of containers and the list of branches to decide which containers should be stopped. Then it calls sh to use the Jenkins agent to stop the containers and remove them.

I think it is simpler to develop, diagnose, and debug if that entire sequence of operations (list branches, list containers, choose containers to stop, stop containers) is performed on the agent inside an sh step that calls a script that runs entirely on the agent. The script that I wrote to do that type of operation in Python looks like this:

#!/usr/bin/python3

import subprocess
import sys

#-----------------------------------------------------------------------

def get_branches():
    ls_remote_lines = subprocess.check_output(['git', 'ls-remote', '--heads', '--refs', '--quiet']).decode('utf-8').split('\n')
    branches = []
    for line in ls_remote_lines:
        if 'refs/' in line:
            sha1, branch_name = line.split('\t')
            branches.append(branch_name.replace('refs/heads/', ''))
    return branches

#-----------------------------------------------------------------------

def get_containers():
    containers_lines = subprocess.check_output(['docker', 'ps', '-a', '--format', '{{.Names}}']).decode('utf-8').split('\n')
    return containers_lines[:-1] # discard trailing empty line

#-----------------------------------------------------------------------

def stop_container(container):
    print("docker stop " + container)

#-----------------------------------------------------------------------

def cleanup_pipeline(args = []):
    branches = get_branches()
    # print('==== Branches ====')
    # for branch in branches:
    #     print(branch)

    containers = get_containers()
    # print('==== Containers ====')
    # for container in containers:
    #     print(container)

    # Stop containers for non-existent branches
    for container in containers:
        found = False
        for branch in branches:
            if branch in container:
                found = True
        if not found:
            stop_container(container)

#-----------------------------------------------------------------------

if __name__ == "__main__": cleanup_pipeline(sys.argv[1:])

The Jenkins project recommends keeping Pipeline scripts simple and pushing as much logic as is feasible into scripts that run on the agent. See the "How to use Jenkins less" talk from Jesse Glick and the "Use just enough pipeline" blog post by Darin Pope and me.

I truly was trying to provide useful information with my comment. My apologies if it was not received as such.