Adding a second project to the list to trigger causes NPE

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major
    • Component/s: core
    • Environment:
      RHEL 6.5 X86_64 Jenkins installed from RPM and updated via yum to 1.563

      Adding a second project to the projects to build in 'Post build Actions'
      results in only the first project being triggered and this message concerning an NPE at the end of the parent log.

      BUILD SUCCESSFUL
      Total time: 7 minutes 40 seconds
      Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
      Triggering a new build of prowess_intel #651
      FATAL: null
      java.lang.NullPointerException
      at hudson.model.Result.isBetterOrEqualTo(Result.java:125)
      at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133)
      at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83)
      at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140)
      at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243)
      at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:674)
      at hudson.model.Build$BuildExecution.cleanUp(Build.java:193)
      at hudson.model.Run.execute(Run.java:1752)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:231)

            Assignee:
            Unassigned
            Reporter:
            Chris Jones
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: