|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
According to the stack trace, what seems to be happening is that the EnvInjectAction.build field is referring to another build object (IOW, not the one that the action is associated with.) In such case, a part of the referenced AbstractBuil}}d object gets sucked into the serialized build.xml, but it's missing some critical transient fields (such as {{Run.project), and that causes this NPE. That's the root cause.
What made the difference between 1.485 and 1.486 is probably that 1.485 recovered gracefully from this failure by letting the job load OK (even though some build records failed to load), and 1.486 didn't do that.
Writing a test to verify this.