The failure can be provoked easily by directly accessing the "buildHistory/all" data for any job irrespective of the number of build records that it has stored. i.e. access to teh

https://ci.jenkins-ci.org/job/jenkins_main_trunk/buildHistory/all

Digging deeper into this issue and the problem is more subtle than HistoryWidget#getRenderList() returning an Iterable that returns null values. In the "all" case it returns the underlying RunList for the job.

Having examined the RunList at runtime I can see that it implements both the Iterable and Map interfaces. It looks like Jelly in core/src/main/resources/hudson/widgets/HistoryWidget/entries.jelly is iterating over this by getting the entrySet() of the map. The individual entries of the entrySet are Map.Entry values rather than the Run entry that we expect. This causes jelly to fail to access the individual components of the entry and eventually causes the NPE that is reported in this bug.

I can see from instrumenting the code that the Jelly iterator in
The problem is that in 1.485 the underlying RunList is now a

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

Reply via email to