I also see this with 1.7 version. I have only 1 build step with two jobs. Both jobs complete successfully, but the main job (the multijob, job) fails due to the below exception:

FATAL: null
java.lang.NullPointerException
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.evaluateResult(MultiJobBuild.java:69)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.isFailure(MultiJobBuild.java:59)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:51)
at hudson.model.Run.execute(Run.java:1516)
at hudson.model.Run.run(Run.java:1462)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)

Thanks for any fix!

I have the same issue with 1.7 version of Jenkins Multijob plugin and Jenkins ver. 1.494.

FATAL: null
java.lang.NullPointerException
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.evaluateResult(MultiJobBuild.java:69)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.isFailure(MultiJobBuild.java:59)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:51)
at hudson.model.Run.execute(Run.java:1543)
at hudson.model.Run.run(Run.java:1489)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)

We have a lot of jobs running in production and we receive an email each time something goes wrong. But with this problem, we receive email every time and I fear we miss a real problem.
So a fix will be very much appreciated !

Hi,
I just send a pull request https://github.com/jenkinsci/tikal-multijob-plugin/pull/14
It is just a fix for the NPE, not for the real problem that seems to be that success build has a null result oO

But with this, success build would not fail because of NPE

is there a fix or a workaround for this?

Code changed in jenkins
User: François Dussert
Path:
src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuild.java
http://jenkins-ci.org/commit/tikal-multijob-plugin/edc4ce080158acd04b29f037b379d4a617b8e937
Log:
Fix https://issues.jenkins-ci.org/browse/JENKINS-16042

Code changed in jenkins
User: Haggai Philip Zagury
Path:
src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuild.java
http://jenkins-ci.org/commit/tikal-multijob-plugin/de71f22cca884732ab23fc7fba2cfa9024392b1a
Log:
Merge pull request #14 from fdussert/master

Fix NPE for https://issues.jenkins-ci.org/browse/JENKINS-16042

Compare: https://github.com/jenkinsci/tikal-multijob-plugin/compare/0803d14e5019...de71f22cca88

For those needing a quick fix a snapshot is here (works for me):

https://buildhive.cloudbees.com/job/jenkinsci/job/tikal-multijob-plugin/org.jenkins-ci.plugins$jenkins-multijob-plugin/

Upload the hpi you downloaded into your jenkins and uninstall the current plugin. Restart.

You will need to check back to the jenkins website regularly to see if a new version has been released. When that occurs remove the snapshot and install the new version.

Fixed in the previous patch