[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 OK, I changed the Read Timeout from 0 (the default, post-upgrade to 3.0.5) to 10, and with that plus the Thread Executors set to 10, I'm now getting the expected behavior on 3.0.5. I'd still like to see a newer version of this plugin (3.0.6?) configure working defaults when upgrading from 3.0.2, but am at least no longer blocked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Olivier Lamy, I still get "issue doesn't exist in JIRA" under 3.0.5, despite setting Thread Executors to 10 and then getting "Success" upon clicking Validate Settings under the Configure System page. A commit message containing a valid JIRA ID does not get annotated on the build page, nor does a comment get added to the JIRA issue. So, this blocker isn't resolved, even if the actual symptoms are different from what was originally reported. I don't know whether there are additional configuration changes that need to be made in order for this to work, but if there are, I'd also comment that a migration from 3.0.2 to 3.0.5 should really provide working defaults (e.g., for Thread Executors), or at least more explicit warnings that people must manually adjust their configuration (and specify how) after upgrading, or their JIRA annotations/commenting simply won't work. I'll try fiddling with a few other settings but if I can't get it working will have to downgrade to 3.0.2 again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy updated JENKINS-54131 Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy updated JENKINS-54131 Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy edited a comment on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 [~milkyman] good to hear!! well I made some fixes and need to cut a release early next week.threadExecutorNumber with value 1 is definitely too low if you have multiple jobs using this JiraSite.My bad I think it was a mistake to make this option configurable so easily people will put wrong valuesI need to fix user help for this value Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Horst Krause good to hear!! well I made some fixes and need to cut a release early next week. threadExecutorNumber with value 1 is definitely too low if you have multiple jobs using this JiraSite. My bad I think it was a mistake to make this option configurable so easily people will put wrong values I need to fix help for this value Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Horst Krause commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I had already threadExecutorNumber with value 1 in the config value. This did not work. I stopped jenkins and changed this to the proposed 10. This did not work too. But perhaps your hint about the readTimeout helped. It was set to 0 in the config. I changed it to 30 and now everything seems to work. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Horst Krause what is the value you used? and what is the value of readTimeout? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title
Horst Krause commented on JENKINS-54131
Re: "Failed to parse changelog" in JIRA plugin 3.0.3
Adding this config param did not help in 3.0.4. I still get the "TimeoutException: Timeout waiting for task" when opening the status page of a build run in the past ("https://jenkins.mycompany/view/myview/job/myjob/121/") where the commit comment contains an issue ID.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I can reproduce now so I'm working on it. Temporary workaround: you can open a file called hudson.plugins.jira.JiraProjectProperty.xml Then within each add 10 Anyway I think it's probably a very bad idea to add this configuration parameter... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Labels: jira-plugin-3.0. 4 5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones reopened an issue The problematic behavior is different in 3.0.4 than in 3.0.3 (as reported in the comments above), but 3.0.4 has issues that are still blockers – it doesn't ultimately solve the problem this issue was reporting, so I'm reopening this. If it makes sense to open a new ticket and put the newer screenshots and console logs there, we could do that instead. Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Nick Jones Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I'm getting the very same error as Hal Deadman. I simply upgraded from 3.0.2 to 3.0.4, with no configuration changes for the JIRA site in Jenkins, and am now getting a "issue doesn't exist in JIRA" message in the console log (referencing the JIRA ID in the commit being built). Additionally – possibly due to the same root cause – I get the threadExecutorNumber error when attempting to Validate Settings. I'll be rolling back to 3.0.2 once more. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 We are getting this warning when we validate settings, even though Thread Executor Size is 1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Hal Deadman Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Paul Holden commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Yes, the current problem I'm experiencing is with 3.0.4 - see my previous comment for the stacktrace, under: Upgrading the plugin to 3.0.4 and triggering another build, with the JIRA issue number in the commit message and I now get the following exception in the Jenkins log, and no posted comment back in JIRA: As far as I know, the configuration for the plugin is correct. I haven't changed any of it since the plugin was last working (in 3.0.2). I've mailed you a screenshot of the configuration, in case that helps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I need to know if you have the same error log with 3.0.4? what happen if you configure correctly the value in the ui? anyway I need some ui screenshots or console logs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Paul Holden commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Hi Olivier Lamy, is there any specific part of my configuration you want to see? Same as Tomas Zaleniakas - the plugin worked fine up until 3.0.2 but has been broken in the two subsequent releases. The configuration for my JIRA site hasn't changed since 3.0.2. Current problem is with the changelog annotator after a triggered build, and when trying to validate settings in admin UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Tomas Zaleniakas with 3.0.4? Can I get a screenshot of the UI and errors logs when trying to annotate. This will help to understand the problem as it should be fixed. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Tomas Zaleniakas edited a comment on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I had to urgently downgrade. But plugin does not work and i get same errors as [~pholden] mentioned when validating and when trying to annotate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Tomas Zaleniakas commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I had to urgently downgrade. But plugin does not work and i get same errors when validating and when trying to annotate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Tomas Zaleniakas what issue do you have exactly? Can you give more details what happened when upgrading to 3.0.4? is it an issue using the configuration screen or only in the logs when activating the plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Tomas Zaleniakas commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Same issue with 3.0.4 as Paul Holden had to downgrade to 3.0.2. Patch version should not require a config change or anything as 3.0.2 worked just fine. Now plugin is broken for two weeks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 can I have a screenshot of your settings? The validation error is definitely here to avoid wrong configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Paul Holden commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 We also saw the following exception in the log for a triggered build, seems related to this issue: WARNING: Error updating JIRA issues. Saving issues for next build. java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at hudson.plugins.jira.Updater.perform(Updater.java:97) at hudson.plugins.jira.JiraIssueUpdater.perform(JiraIssueUpdater.java:64) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1844) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Oct 26, 2018 3:57:51 PM hudson.scm.ChangeLogSet$Entry getMsgAnnotated INFO: ChangeLogAnnotator hudson.plugins.jira.JiraChangeLogAnnotator@6c5afa failed to annotate message 'MEDIA-679 fix the thing'; null Re-running the job manually did pass, but as mentioned by Nick Jones, nothing happened re. "Saving issues for next build" Upgrading the plugin to 3.0.4 and triggering another build, with the JIRA issue number in the commit message and I now get the following exception in the Jenkins log, and no posted comment back in JIRA: WARNING: jira rest client get project keys error. cause: Timeout waiting for task. java.util.concurrent.TimeoutException: Timeout waiting for task. at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259) 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.getProjectsKeys(JiraRestService.java:179) at hudson.plugins.jira.JiraSession.getProjectKeys(JiraSession.java:64) at hudson.plugins.jira.JiraSite.getProjectKeys(JiraSite.java:713) at hudson.plugins.jira.JiraChangeLogAnnotator.hasProjectForIssue(JiraChangeLogAnnotator.java:146) at hudson.plugins.jira.JiraChangeLogAnnotator.annotate(JiraChangeLogAnnotator.java:75) at hudson.scm.ChangeLogSet$Entry.getMsgAnnotated(ChangeLogSet.java:252) at sun.reflect.NativeMethodAccessorImpl.i
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy resolved as Fixed Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Labels: jira-plugin-3.0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title
Hal Deadman edited a comment on JENKINS-54131
Re: "Failed to parse changelog" in JIRA plugin 3.0.3
We are getting similar error when we run the following from a pipeline:jiraComment body: env.runningComment, issueKey: env.jiraIssueId { color code : #9a java } [Pipeline] jiraComment{color}Error jiraCommentError when executing success post condition:java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:80) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:64) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) {code} We downgraded to 3.0.2 and the error didn't happen.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 We are getting similar error when we run the following from a pipeline: jiraComment body: env.runningComment, issueKey: env.jiraIssueId [Pipeline] jiraCommentError when executing success post condition: java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:80) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:64) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) We downgraded to 3.0.2 and the error didn't happen. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Hal Deadman Attachment: Attachment.url Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Hal Deadman updated an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Hal Deadman Attachment: Attachment.url Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title
Benjamin Coover commented on JENKINS-54131
Re: "Failed to parse changelog" in JIRA plugin 3.0.3
Seeing this as well, but in a different context. It only appears to be happening from automatically triggered builds, I have yet to see a build fail for this reason that I started manually. I did some digging using the stack trace and found the same thing that Matthew Kelly mentions in JENKINS-54144. The offending section appears to be here, in jira-plugin-jira-3.0.3/src/main/java/hudson/plugins/jira/JiraSite.java:457
if (executorService==null){
executorService = Executors.newFixedThreadPool(
threadExecutorNumber, //
new ThreadFactory()
{
final AtomicInteger threadNumber = new AtomicInteger( 0 );
@Override
public Thread newThread( Runnable r )
{
return new Thread( r, "jira-plugin-http-request-" + threadNumber.getAndIncrement() + "-thread" );
}
} );
}
According to the docs, IllegalArgumentException is thrown if "nThreads" ("threadExecutorNumber" here) is 0, so something appears to be setting this value to 0 on triggered builds, but not manual builds.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Matthew Kelly commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I also have the same issue, and raised it here as well: JENKINS-54144 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Simply rerunning appeared _to work – i.e., the build succeeded – but it didn't actually "save issues for the next build" (despite the log message to that effect), so didn't actually attempt to parse the changelog again, which avoided the error. If I made a new commit with a JIRA ID in it, _then reran the build, it failed again. 3.0.2 has been stable so far since reverting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones edited a comment on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Simply rerunning _appeared _to _appeared_ to work -- i.e., the build succeeded -- but it didn't actually "save issues for the next build" (despite the log message to that effect), so didn't actually attempt to parse the changelog again, which avoided the error. If I made a new commit with a JIRA ID in it, _then_ reran the build, it failed again. 3.0.2 has been stable so far since reverting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Brian DeBlis commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I get the same error, but if I re-run a second time, it works. It is just that first run for a triggered build that makes it fail. I am also reverting back to 3.0.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-10-17 14:22 Environment: JIRA 3.0.3, Blue Ocean 1.9.0 Priority: Blocker Reporter: Nick Jones Testing the updating of Jira issues with the Jira 3.0.3 plugin, I get the following stack trace: java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:45) at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) Caused: java.io.IOException: Failed to parse changelog at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:4
