Issue

• Jenkins logs are growing, polluted with NullPointerExceptions like the following:

2019-01-14 22:23:56.051+0000 [id=15]	WARNING	hudson.model.Run#onLoad: failed to load {} from /var/jenkins_home/jobs/folder/jobs/multibranch/branches/master/builds/1/build.xml
java.lang.NullPointerException
	at com.cloudbees.devoptics.deliver.events.RunEventLog.close(RunEventLog.java:220)
	at com.cloudbees.devoptics.deliver.events.RunEventLog.onLoad(RunEventLog.java:201)
	at hudson.model.Run.onLoad(Run.java:364)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:734)
	at hudson.model.RunMap.retrieve(RunMap.java:225)
	at hudson.model.RunMap.retrieve(RunMap.java:57)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:499)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:481)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:379)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344)
	at jenkins.model.lazy.LazyBuildMixIn$RunMixIn.getPreviousBuild(LazyBuildMixIn.java:371)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.getPreviousBuild(WorkflowRun.java:267)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.getPreviousBuild(WorkflowRun.java:140)
	at hudson.model.RunMap$1.next(RunMap.java:110)
	at hudson.model.RunMap$1.next(RunMap.java:99)

Environment

• CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
• CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
• CloudBees CI (CloudBees Core) on traditional platforms - Client controller
• CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
• CloudBees Jenkins Enterprise
• CloudBees Jenkins Enterprise - Managed controller
• CloudBees Jenkins Enterprise - Operations Center
• CloudBees Jenkins Team
• CloudBees Jenkins Platform - Client controller
• CloudBees Jenkins Platform - Operations Center
• Jenkins LTS
• CloudBees DevOptics Plugin between 1.1609 and 1.1617 (excluded)

Related Issue(s)

• DEVOPTICS-610

Resolution

The problem is caused by the CloudBees DevOptics Plugin since version 1.1609 and due to a serialization issue. This could well impact Jenkins performances when it is under load since this exception happens whenever a Pipeline build is loaded.

Solution

Upgrade CloudBees DevOptics Plugin to 1.1617 or later