Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49819

FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue

      When I want Jenkins to create a JIRA issue for a failed Test, I get the following FATAL error:
      FATAL: org.apache.http.impl.client.cache.CacheConfig.setNeverCache1_0ResponsesWithQueryString(Z)V
      java.lang.NoSuchMethodError: org.apache.http.impl.client.cache.CacheConfig.setNeverCache1_0ResponsesWithQueryString(Z)V
      at com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClient.<init>(DefaultHttpClient.java:155)
      at com.atlassian.jira.rest.client.internal.async.AsynchronousHttpClientFactory.createClient(AsynchronousHttpClientFactory.java:53)
      at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.create(AsynchronousJiraRestClientFactory.java:35)
      at com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.createWithBasicHttpAuthentication(AsynchronousJiraRestClientFactory.java:42)
      at rocks.inspectit.releaseplugin.JIRAAccessTool.connect(JIRAAccessTool.java:185)
      at rocks.inspectit.releaseplugin.JIRAAccessTool.<init>(JIRAAccessTool.java:116)
      at rocks.inspectit.releaseplugin.ticketing.JIRATicketEditor.perform(JIRATicketEditor.java:72)
      at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
      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:1727)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:97)
      at hudson.model.Executor.run(Executor.java:429
      I tried to go back to 2.0.5, but it doesn't work. Is there something wrong in my configuration? On the setup page (System Configuration), I get iTask as response from JIRA when I press the button to test my credentials. So, my password seems to be correct, right?

      We are using JIRA version 6.4.12.

      The creation of JIRA issues out of Jenkins worked before, but I cannot tell since when it doesnt't work any more.

          [JENKINS-49819] FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue

          Catalin Luta added a comment -

          Hey michaelmotteler, thanks for opening the issue! Did you restart Jenkins after updating to 2.0.6? We've changed some things related to the HttpClient and I'm thinking that some classes did not get updated. Let me know if it works after a restart.

          Catalin Luta added a comment - Hey michaelmotteler , thanks for opening the issue! Did you restart Jenkins after updating to 2.0.6? We've changed some things related to the HttpClient and I'm thinking that some classes did not get updated. Let me know if it works after a restart.

          Michael M. added a comment -

          Hi catalinluta, yes I have restarted Jenkins serveral times. I usually restart it after any plugin update or Jenkins update. So, a restart did not help in my case.

          Michael M. added a comment - Hi catalinluta , yes I have restarted Jenkins serveral times. I usually restart it after any plugin update or Jenkins update. So, a restart did not help in my case.

          Catalin Luta added a comment -

          Hey michaelmotteler. Sorry for the long pause. We've had a rough patch at work and couldn't look into it. We have some time next week and we'll get back to you as soon as we can.

          Catalin Luta added a comment - Hey michaelmotteler . Sorry for the long pause. We've had a rough patch at work and couldn't look into it. We have some time next week and we'll get back to you as soon as we can.

          Catalin Luta added a comment -

          michaelmotteler, manus, we've tried replicating this on a vanilla installation of Jenkins 2.106, but it worked fine. We are also using it in prod on 2.107. Could you please give us some more details about your setup? Have you tried any other versions? Was it, in both cases, an update, or was it a new installation of the plugin? Anything that would help us replicate this would be great.

          Catalin Luta added a comment - michaelmotteler , manus , we've tried replicating this on a vanilla installation of Jenkins 2.106, but it worked fine. We are also using it in prod on 2.107. Could you please give us some more details about your setup? Have you tried any other versions? Was it, in both cases, an update, or was it a new installation of the plugin? Anything that would help us replicate this would be great.

          Michael M. added a comment -

          catalinluta, what kind of Info do you need more? I am using the latest Jenkins 2.122 at the moment. The problem still exists (see problem description). As I am using this plugin since months, it must have come in via update - so no new installation.

          Michael M. added a comment - catalinluta , what kind of Info do you need more? I am using the latest Jenkins 2.122 at the moment. The problem still exists (see problem description). As I am using this plugin since months, it must have come in via update - so no new installation.

          Christian added a comment -

          michaelmotteler Is this issue still relevant?

          Christian added a comment - michaelmotteler Is this issue still relevant?

            catalinluta Catalin Luta
            michaelmotteler Michael M.
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: