[
https://issues.jenkins-ci.org/browse/JENKINS-12617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158597#comment-158597
]
Daniel Rohlfing commented on JENKINS-12617:
-------------------------------------------
About 8 projects where affected. All these config.xml files have the same
modification timestamp, but there are some with an older one which still
working correctly (because they have an existing <publishers> tag).
> java.lang.NullPointerException on missing <publishers> in project config
> ------------------------------------------------------------------------
>
> Key: JENKINS-12617
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12617
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Environment: JRE 1.7.0_02-b13 / WinXP32 german
> Reporter: Daniel Rohlfing
> Attachments: config.xml
>
>
> Old projects, who don't have a <publishers> tag in their config.xml will
> crash while loading on statup:
> {noformat}
> ←[0m←[31mFeb 01, 2012 7:12:36 PM jenkins.InitReactorRunner$1 onTaskFailed
> Schwerwiegend: Failed Loading job MyProjectName
> java.lang.NullPointerException
> at hudson.model.Project.createTransientActions(Project.java:207)
> at
> hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602)
> at hudson.model.AbstractProject.onLoad(AbstractProject.java:272)
> at hudson.model.Project.onLoad(Project.java:88)
> at hudson.model.Items.load(Items.java:115)
> at jenkins.model.Jenkins$14.run(Jenkins.java:2372)
> at
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
> at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
> at jenkins.model.Jenkins$5.runTask(Jenkins.java:812)
> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
> at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {noformat}
> I'm currently using v1.450, but at least v1.449 is affected too. I'm not sure
> which upgrade step has introduced this problem, because I only lost some old
> minor important projects and I havn't noticed it immediately. It seems that
> the affected config.xml are touched the last time at 2011-12-08. So I thing
> it was v1.442, which made it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
