Observed in a DEV@cloud server:
Started by an SCM change
FATAL: null
java.lang.NullPointerException
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:549)
at hudson.model.Run.execute(Run.java:1665)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
Looks like getCurrentNode is returning null for some reason, perhaps due to a slave going offline just as the build is starting. Should be handled more gracefully.