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

Pipeline Intermittent "Error grabbing Grapes" Issues

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Intermittently, when a pipeline uses the "@Grab" notation, it results in the following error: 
      java.lang.RuntimeException: Error grabbing Grapes – [unresolved dependency: commons-codec#commons-codec;1.9: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)] 

      If this is related to GROOVY-7407, perhaps the recommended WorkaroundGroovy7407WrappingGrapeEngine.java could be imported into workflow-cps-global-lib and called the first time a trusted library is loaded (before it can attempt to grab anything)?

       

        Attachments

          Issue Links

            Activity

            Hide
            sag47 Sam Gleske added a comment -

            This is reliably reproducible if one runs a multibranch pipeline with multiple branches building concurrently attempting to Grab via a globally configured pipeline library.

            Here's an example: https://github.com/samrocketman/jenkins-bootstrap-jervis/issues/19

            Show
            sag47 Sam Gleske added a comment - This is reliably reproducible if one runs a multibranch pipeline with multiple branches building concurrently attempting to Grab via a globally configured pipeline library. Here's an example:  https://github.com/samrocketman/jenkins-bootstrap-jervis/issues/19
            Hide
            svanoort Sam Van Oort added a comment -

            FWIW I consider this one to carry nontrivial risk of breaking libraries or triggering memory leaks or deadlocks... for now I'm going to wait to see if the Groovy community pulls in the fix and we can consume it downstream. 

             

            Will leave the JIRA open for now in case someone from the community is bold enough to take this up and give it a try.  It's probably pretty simple to apply the change... but testing it and debugging might be a real challenge.

            Show
            svanoort Sam Van Oort added a comment - FWIW I consider this one to carry nontrivial risk of breaking libraries or triggering memory leaks or deadlocks... for now I'm going to wait to see if the Groovy community pulls in the fix and we can consume it downstream.    Will leave the JIRA open for now in case someone from the community is bold enough to take this up and give it a try.  It's probably pretty simple to apply the change... but testing it and debugging might be a real challenge.

              People

              • Assignee:
                Unassigned
                Reporter:
                stevendeal Steven Deal
              • Votes:
                4 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: