-
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.
[JENKINS-23277] NPE from AbstractBuild$AbstractBuildExecution.run
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: cloud exception nullpointer robustness | New: cloud exception lts-candidate nullpointer robustness |
Labels | Original: cloud exception lts-candidate nullpointer robustness | New: 1.565.1-fixed cloud exception nullpointer robustness |
Workflow | Original: JNJira [ 155840 ] | New: JNJira + In-Review [ 195266 ] |