Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: 06c211c6b425e313f808f9cbdd49d32f9c922a84
https://github.com/jenkinsci/jenkins/commit/06c211c6b425e313f808f9cbdd49d32f9c922a84
Author: Jesse Glick <[email protected]>
Date: 2013-07-10 (Wed, 10 Jul 2013)
Changed paths:
M changelog.html
M core/src/main/java/hudson/matrix/MatrixConfiguration.java
M core/src/main/java/hudson/model/AbstractProject.java
M core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
Log Message:
-----------
[JENKINS-17728] Fixing another possible cause of an NPE.
Unlike the bug I originally reproduced, in which the parent had some builds
but the context in which the new build was scheduled omits a parent,
this seems to be due to a case in which there is no build record at all for the
parent.
No idea how that could happen (getLastBuild should return even a running,
failed, or aborted build),
but @treydock reports a stack trace in 1.509.2 which implies this.
So fixing null safety; will not prevent an exception but will report it more
gracefully.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
