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

BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • build-flow-plugin
    • build-flow 0.5
      jenkins 1.491

      Hi,
      we implemented our build pipeline with build-flow. The pipeline has several parallel and serial configured jobs. Since we are using this plugin, we are noticing randomly appearing build breaks.

      The stacktrace starts with org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.acceptGetProperty(GetEffectivePojoPropertySite.java:51), thus i'm supposing a relation between the NPE and the parameter that is set with every job i run. It's representing a global build number that is used throught the whole pipeline.

      The configuration and console output is attached below. The build (only the buildflow job) always breaks after the big parallel execution part. It occurs in about every fifth build. Because the build is triggered multiple times a day due to the continuous delivery pattern and lasts 30 minutes , this bug is really annoying -> high priority

        1. build-cfg.txt
          1 kB
        2. console-output.txt
          8 kB

          [JENKINS-15519] BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException

          Scott Sandler added a comment -

          I'm seeing this issue intermittently as well, same exact stack trace.

          Scott Sandler added a comment - I'm seeing this issue intermittently as well, same exact stack trace.

          Erik Lovlie added a comment -

          Same here. Stack trace is nearly the same.

          Erik Lovlie added a comment - Same here. Stack trace is nearly the same.

          Ulf Bamberg added a comment -

          i noticed there's a similar bug report: https://issues.jenkins-ci.org/browse/JENKINS-13915

          Ulf Bamberg added a comment - i noticed there's a similar bug report: https://issues.jenkins-ci.org/browse/JENKINS-13915

          Ben Golding added a comment -

          (copy of my comment from JENKINS-13915)

          This issue was happening on 100% of builds for me.
          Since updating 0.5 to 0.6 yesterday, the exception is gone.

          I guess more time is needed in case this is an intermittent issue as some users are reporting.

          Ben Golding added a comment - (copy of my comment from JENKINS-13915 ) This issue was happening on 100% of builds for me. Since updating 0.5 to 0.6 yesterday, the exception is gone. I guess more time is needed in case this is an intermittent issue as some users are reporting.

          Ben Golding added a comment -

          Stacktrace and user comments seem the same as JENKINS-13915: marking this one as a duplicate (JENKINS-13915 is older)

          Ben Golding added a comment - Stacktrace and user comments seem the same as JENKINS-13915 : marking this one as a duplicate ( JENKINS-13915 is older)

          Ben Golding added a comment -

          JENKINS-13915 now marked fixed (in 0.8), also marking this one as fixed.

          Ben Golding added a comment - JENKINS-13915 now marked fixed (in 0.8), also marking this one as fixed.

            ndeloof Nicolas De Loof
            vvurst Ulf Bamberg
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: