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

Map collectEntries closure not behaving correctly

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: pipeline
    • Labels:
      None
    • Environment:
      Jenkins 1.6.11
    • Similar Issues:

      Description

      The collectEntries method on Groovy Maps returns an ArrayList instead of a Map, failing its basic function contract. Unknown if this is specific to the workflow plugin or a general issue with Groovy in Jenkins.

      1-line test case from Map.collectEntries documentation:
      assert [a:1, b:2].collectEntries

      { key, value -> [value, key] }

      == [1:'a', 2:'b']

      This may be related to https://issues.jenkins-ci.org/browse/JENKINS-26481 and may be indicative of a general mishandling of Groovy contexts.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                sumdumgai A C
              • Votes:
                3 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: