Kohsuke's updated summary

In 1.485, there's a bug that causes Jenkins to return null when someone is listing historical build records. The caller is not expecting null return value, so this normally results in NullPointerException.

Because there are numerous code inside Jenkins that touches build history, such NullPointerException can occur in a large number of different places.

If you are not sure your NullPointerException is just another manifestation of this bug or an unrelated bug, please feel free to file a separate ticket, and mention this ticket as a possible cause so that the plugin developers won't get confused.

Original bug report

running the build fails with the following error:

ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com
java.lang.NullPointerException
at hudson.tasks.LogRotator.perform(LogRotator.java:119)
at hudson.model.Job.logRotate(Job.java:338)
at hudson.model.Run.execute(Run.java:1581)
at hudson.maven.MavenBuild.access$600(MavenBuild.java:83)
at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:545)
at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:794)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:589)
at hudson.model.Run.execute(Run.java:1516)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
project=hudson.maven.MavenModuleSet@280d8b87[deploy sdk]