[JIRA] (JENKINS-49819) FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue
Title: Message Title Michael M. commented on JENKINS-49819 Re: FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue Catalin Luta, 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49819) FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue
Title: Message Title Michael M. commented on JENKINS-49819 Re: FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue Hi Catalin Luta, 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49819) FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue
Title: Message Title Michael M. created an issue Jenkins / JENKINS-49819 FATAL Error in JiraTestResultReporter 2.0.6 when trying to create a Jira Issue Issue Type: Bug Assignee: Catalin Luta Components: jiratestresultreporter-plugin Created: 2018-03-01 06:43 Environment: Windows, Jenkins 2.106 Priority: Minor Reporter: Michael M. 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.(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.(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(R
[JIRA] (JENKINS-43673) Need new trigger for Parameterized Trigger Plugin: Failed but not still failing
Title: Message Title Michael M. commented on JENKINS-43673 Re: Need new trigger for Parameterized Trigger Plugin: Failed but not still failing I would really like to have this trigger. I want to trigger an action when a periodic test fails the first time. It is clear in the next test runs that the test again will fail unless, I have fixed the bug. It would be very helpful for me to have this trigger. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43673) Need new trigger for Parameterized Trigger Plugin: Failed but not still failing
Title: Message Title Michael M. updated an issue Jenkins / JENKINS-43673 Need new trigger for Parameterized Trigger Plugin: Failed but not still failing Change By: Michael M. Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9146) Allow archiving of empty directories to be enabled/disabled
Title: Message Title Michael M. commented on JENKINS-9146 Re: Allow archiving of empty directories to be enabled/disabled I also would be very happy, if empty directories could be part of an artefact. The most flexible way in my oppinion would be to add as extra option in the advanced section. Then every user is free to enable / disable this functionality. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
