Well, the problem is indeed caused by the latest version of the JobConfigHistory plugin. It happens when you start to build a project which has no configuration history yet. I'll try to release a hotfix version today. As a workaround right now you can just change something in the configuration of the project (like the description or disable/enable) and then it should work.
Kathi Stutz On 22.01.2013 13:52, Riccardo Foschia wrote: > Just a guess: As the stacktrace suggests the problem seems to be caused > by the JobConfigHistory plugin. Try to update this plugin to a newer > version. > > As experience shows after an upgrade of Jenkins it is often necessary to > upgrade some plugins. > > Regards, > Riccardo > > Am 22.01.2013 13:09, schrieb David Aldrich: >> Hi >> >> This morning I upgraded Jenkins from 1.480.1 to 1.480.2 and restarted >> Jenkins. Now one of my jobs fails with: >> >> >> Started by user <me> >> >> FATAL: null >> >> java.util.NoSuchElementException<http://stacktrace.jenkins-ci.org/search?query=java.util.NoSuchElementException> >> >> at java.util.AbstractList$Itr.next(Unknown Source) >> >> at java.util.Collections.min(Unknown Source) >> >> at >> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:79) >> >> at >> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:27) >> >> at >> hudson.model.listeners.RunListener.fireStarted(RunListener.java:188) >> >> at hudson.model.Run.execute(Run.java:1497) >> >> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) >> >> at >> hudson.model.ResourceController.execute(ResourceController.java:88) >> >> at hudson.model.Executor.run(Executor.java:236) >> >> How can I fix this please? >> >> Best regards >> >> David >> >>
