Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.2.2
    • Component/s: None
    • Labels:
      None

      Description

      After looking at the source code for the Jenkins plugin, it appears that a new ArrayList() is still being used instead of a concurrent safe data structure. This appears to be causing the exceptions on our build systems

      Errors thrown prior to plugin crashing

      [Pipeline] End of Pipeline
      an exception which occurred:
      in field java.util.Collections$SynchronizedCollection.c
      in object java.util.Collections$SynchronizedList@b960033e
      in field org.jfrog.hudson.pipeline.common.types.buildInfo.BuildInfo.modules
      in object org.jfrog.hudson.pipeline.common.types.buildInfo.BuildInfo@69af4dab
      in field groovy.lang.Closure.delegate
      in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@776996f4
      in field groovy.lang.Closure.delegate
      in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@24128ba
      in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.closures
      in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@c4803fe
      in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@c4803fe
      Caused: java.util.ConcurrentModificationException
      

        Attachments

          Activity

            People

            • Assignee:
              eyalb Eyal Ben Moshe
              Reporter:
              davidx David Xu
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: