[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Upgraded to latest Jenkins ver. 1.492 today and the "More" link to additional builds is fixed as well as the "buildHistory/all" API. Thanks! 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
dogfood commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Integrated in jenkins_main_trunk #2084 FIXED JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException (Revision e429b6979b5d7361168a743c9e32801e2a9b) Result = SUCCESS kohsuke : e429b6979b5d7361168a743c9e32801e2a9b Files : changelog.html core/src/main/java/hudson/widgets/HistoryWidget.java 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
SCM/JIRA link daemon resolved JENKINS-15499 as Fixed HistoryWidget/entry.jelly throws NullPointerException Change By: SCM/JIRA link daemon (17/Nov/12 7:01 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer assigned JENKINS-15499 to Richard Mortimer HistoryWidget/entry.jelly throws NullPointerException Change By: Richard Mortimer (16/Nov/12 9:42 PM) Assignee: KohsukeKawaguchi RichardMortimer 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Sergey Smirnov updated JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Change By: Sergey Smirnov (14/Nov/12 12:26 PM) Priority: Major Critical 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Thomas Oeding commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Prio should be Critical, breaks a lot of reporting scripts. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException The only way I could get this to work was to roll back to version 1.484 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Tamas Papp commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException When I tried to do that, I got various errors. Should it work fine? 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Mine rolled back without any issues. I diffed the client slave.jar files between 1.484 and 1.489 and they were identical so all I had to do was install the 1.484 jenkins war on the server. Our server is on Ubuntu so all I did was shutdown jenkins, remove the old exploded war/cache, copy the 1.484 war in place and restarted jenkins. Everything came back fine and the "more" links were working again and my API build history scripts worked again. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Sergey Smirnov commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Jenkins ver. 1.489 has the same bug. Any workaround? 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Is there any update on this? 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
S Daigle edited a comment on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Is there any update on this? We also use the API and now all the jobs we have that try accessing the complete build history are failing: wget --no-check-certificate --auth-no-challenge https://jenkins/ci/job/MYBUILD/buildHistory/all -2012-11-08 07:24:07- https://jenkins/ci/job/MYBUILD/all Resolving jenkins... 127.0.1.1, 10.0.0.70 Connecting to jenkins|127.0.1.1|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2012-11-08 07:24:07 ERROR 500: Internal Server Error. If I do not specify the "/all" attribute, it returns successfully. We are running the latest 1.489 version as well. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
David Gersht commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException The error is still there in 1.489 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Ben McDonie commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException I am also seeing this error in 1.489 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Patanachai Tangchaisin commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException The error is still there in 1.488 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Thomas Oeding commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException the same for 1.487 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
taksan commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException I confirm that this error is still happening on 1.487. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
eguess74 commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException i confirm i can see that error in 1.486 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Noam Tamim commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Is there a workaround? Anything? Even a CGI script that directly parses the build history files is ok. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException For the record I checked in working 1.484 (pre-lazy loading support) and there the HistoryWidget baseList element is a hudson.util.RunList but in broken 1.485 and later it is an instance of hudson.model.RunMap. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer assigned JENKINS-15499 to Kohsuke Kawaguchi HistoryWidget/entry.jelly throws NullPointerException I think that this change in behaviour came about by the change to using lazy loading of build records. Due to this change the RunList is now a RunMap which implements Map and hence causes the problem. This needs Kohsuke's input because I suspect the fix needs to be made carefully to somehow hide the map because I'm sure that there is lots of Jelly code that will be otherwise silently broken too. Change By: Richard Mortimer (17/Oct/12 11:54 AM) Assignee: KohsukeKawaguchi 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException See https://github.com/oldelvet/jenkins/tree/jenkins-15499-demo for an example that fixes the specific HistoryWidget problem. I don't intend that this as a final fix but provide it to highlight that wrapping the iterable in a clean class restores previous working behaviour. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer
commented on JENKINS-15499
HistoryWidget/entry.jelly throws NullPointerException
Looking at the output from an affected job the /job/hudson8462/buildHistory/all output contains a link to the console output which contains //console.
tr class="build-row no-wrap "tda href="" class="code-quote">"/job/hudson8462//console"
The build number should be between the // so that suggests that ${build} is null in /hudson/widgets/HistoryWidget/entry.jelly
That in turn means that getRenderList() in HistoryWidget.java is returning null values in the list.
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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Itaru Ogawa commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException I saw the exact same error even with 1.486. Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/ROOT/WEB-INF/lib/jenkins-core-1.486.jar!/hudson/widgets/HistoryWidget/entry.jelly:39:106: i:formatDate java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/ROOT/WEB-INF/lib/jenkins-core-1.486.jar!/hudson/widgets/HistoryWidget/entry.jelly:39:106: i:formatDate java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) ... 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Hansen Loke commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Updated to 1.486 and the issue is still there, similar backtrace. 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Hansen Loke commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException I get this error after upgrading to Jenkins 1.485 too 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
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer commented on JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException There is/was a critical bug or two in 1.485 related to the lazy loading. See JENKINS-15465 and JENKINS-15439. I'm pretty sure that those are the issues that you are seeing. Kohsuke backported the fixes to the 1.486 release candidate build. You can download a pre-release build from https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_rc_branch/279/ 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
