JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist

[Michal Turecki]

We are using JIRA plugin on Jenkins to comment on JIRA issues about build status. Since we have not done any infrastructure changes on 17th and 18th I suspect some JIRA update caused the official JIRA plugin to fail with the message as below:

ABC-1234 issue doesn't exist in JIRA

 To be sure I updated Jenkins along with all it's plugins to the latest versions, re-generated API key for the user in question - it made no difference.

Using curl/postman I could successfuly query the issue details by directly requesting from the API. Changing the Jenkins JIRA plugin issue selector regex to the default one (replacing empty with regex suggested in help) did not make any difference.

Captcha error response header is absent in the response to API call.

What else can I try to make it work?

[Luis Ehlen]

I noticed the same issue on the same dates.

[Michal Turecki]

Thanks for confirming it, hope someone knows whats up as jenkins jira plugin has no issue tracker enabled AFAIK.

[igor_epstein]

Actually they have an issue tracker, although not on Github. Here is a link to another issue on their tracker that may be relevant for you (but not for me, as our company doesn't use proxy):

https://issues.jenkins-ci.org/browse/JENKINS-51522

[Michal Turecki]

Thank you, I thought Jenkins Jira tracker is for jenkins only but it seems plugins are also covered. I reported the issue there as the one you mentioned although relevant has been closed in 2018 - https://issues.jenkins-ci.org/browse/JENKINS-61311

[igor_epstein]

The developers released a new, 3.0.13, version that is based on the latest Jira's API, that should fix these issues

[Luis Ehlen]

That worked for me!
Thanks!

[Josh Brozen]

Also having an issue but am not getting an error or alert in Jenkins console like this:

ABC-1234 issue doesn't exist in JIRA

 With that said, we are seeing this error in the Jenkins logs:

Mar 03, 2020 8:05:26 PM WARNING hudson.plugins.jira.JiraRestService getIssuesFromJqlSearch

jira rest client get issue from jql search error. cause: RestClientException{statusCode=Optional.absent(), errorCollections=[]}
org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.
 at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360)
 at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487)
 at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192)
 at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:34)
 at com.atlassian.jira.rest.client.internal.json.UserJsonParser.parse(UserJsonParser.java:31)
 at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.getOptionalNestedField(IssueJsonParser.java:300)
 at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:234)
 at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:88)
 at com.atlassian.jira.rest.client.internal.json.GenericJsonArrayParser.parse(GenericJsonArrayParser.java:39)
 at com.atlassian.jira.rest.client.internal.json.SearchResultJsonParser.parse(SearchResultJsonParser.java:40)
 at com.atlassian.jira.rest.client.internal.json.SearchResultJsonParser.parse(SearchResultJsonParser.java:27)
 at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$1.handle(AbstractAsynchronousRestClient.java:148)
 at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:189)
Caused: RestClientException{statusCode=Optional.absent(), errorCollections=[]}
 at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:191)
 at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:185)
 at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:81)
 at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:11)
 at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:295)
 at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:185)
 at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
 at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
 at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
 at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
 at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
 at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
 at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:295)
 at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:185)
 at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
 at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
 at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
 at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
 at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
 at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
 at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1.lambda$doCompleted$0(SettableFuturePromiseHttpPromiseAsyncClient.java:41)
 at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.lambda$run$0(SettableFuturePromiseHttpPromiseAsyncClient.java:150)
 at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:69)
 at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run(SettableFuturePromiseHttpPromiseAsyncClient.java:150)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
Caused: java.util.concurrent.ExecutionException
 at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
 at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:262)
 at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
 at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
 at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)
 at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:197)
 at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)
 at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:1043)
 at hudson.plugins.jira.JiraIssueUpdateBuilder.perform(JiraIssueUpdateBuilder.java:105)
 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)
 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
 at hudson.model.Build$BuildExecution.build(Build.java:206)
 at hudson.model.Build$BuildExecution.doRun(Build.java:163)
 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
 at hudson.model.Run.execute(Run.java:1880)
 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
 at hudson.model.ResourceController.execute(ResourceController.java:97)
 at hudson.model.Executor.run(Executor.java:428)

 On latest version of JIRA Plug-in (3.0.12) and CURL commands all work fine

Related issues: https://community.atlassian.com/t5/Jira-questions/jira-rest-java-client-core-5-1-6-and-JSONException/qaq-p/1303781

https://community.atlassian.com/t5/Jira-questions/REST-API-numerous-calls-now-throwing-an-error/qaq-p/1305234

[Luis Ehlen]

I have the latest version of the plugin and it fails for me

[Michal Turecki]

@Luis EhlenIt must be the custom build of the plugin from the pull request here: https://issues.jenkins-ci.org/browse/JENKINS-56987?focusedCommentId=386448&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-386448

[Michal Turecki]

@Luis EhlenI have uploaded my personal build, just replace jira.jpi with it: https://speedwelluk-my.sharepoint.com/:u:/g/personal/mturecki_speedwellsoftware_com/EfXbJ1y-SkBNtKnoJSVCs_8BeF909a8I6zGXM_7IxolkmQ?e=BkqLyK