Memory leak in Jenkins JobDSL

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: continuous integration

      Problem

      While running the JobDSL scripts in Jenkins, after some time, Jenkins is restarted by Kubernetes cos a Java OOM is happening.
      The problem is known by the Jenkins devs, see JENKINS-37213.
      To get rid of the leak, we would have to upgrade to Jenkins 2.60+ but then other problems occur.
      The devs suggest to use the java system property -Dgroovy.use.classvalue=true while starting Jenkins.

      AT
      • add -Dgroovy.use.classvalue=true to Jenkins JAVA_OPTS to reduce memory leakage

        This is the controller panel for Smart Panels app

              Assignee:
              Samuel
              Reporter:
              Christian
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: