[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided

andreas.nusser+jenkins@gmail.com (JIRA)

unread,

Mar 24, 2020, 7:19:04 AM3/24/20

to jenkinsc...@googlegroups.com

Andreas Nusser created an issue

Jenkins /

JENKINS-61661

Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided

Issue Type:	Improvement
Assignee:	Unassigned
Components:	jira-plugin
Created:	2020-03-24 11:18
Environment:	Jenkins 2.226 OpenJdk 1.8 CentOS Linux release 7.7.1908 (Core) Installed via YUM Plugins: Jira Plugin 3.0.13
Priority:	Minor
Reporter:	Andreas Nusser

When not configuring any credentials but a URL for the Jira Plugin, it still tries to connect to the URL. This results in a lot of InvalidCacheLoadException

 
                                                                2020-03-16 02:22:09.137+0000 [id=7306028]	WARNING	h.model.listeners.RunListener#report: RunListener failed
com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key UCS-154.
	at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383)
	at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351)
	at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)
	at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)
	at com.google.common.cache.LocalCache.get(LocalCache.java:3965)
	at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764)
	at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:873)
	at hudson.plugins.jira.JiraJobAction.setAction(JiraJobAction.java:99)
	at hudson.plugins.jira.JiraJobAction$RunListenerImpl.onStarted(JiraJobAction.java:130)
	at hudson.plugins.jira.JiraJobAction$RunListenerImpl.onStarted(JiraJobAction.java:122)
	at hudson.model.listeners.RunListener.fireStarted(RunListener.java:238)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:295)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:428) 
                                                            

It will try to connect for every Jira KEY it finds. This can be a lot of exceptions.

I know, that I should provide credentials if I intend to use the plugin. The real problem is that it was not easy to link this exception to the missing credentials. A nice error message would have been much better than some generic stack trace.