-
Bug
-
Resolution: Fixed
-
Major
-
1.532.x
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.
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/model/AbstractBuild.java
core/src/main/java/hudson/model/Executor.java
http://jenkins-ci.org/commit/jenkins/3f8fc4e2ec5b1b421e1551a2a2fc2a284be330d1
Log:
[FIXED JENKINS-23277] Better diagnosis for an NPE probably involving cloud slaves.