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

"Failed to parse changelog" in JIRA plugin 3.0.3

    XMLWordPrintable

Details

    Description

      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.<init>(ThreadPoolExecutor.java:1314) 
      	at java.util.concurrent.ThreadPoolExecutor.<init>(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:429) 
      Error updating JIRA issues. Saving issues for next build.
      java.lang.IllegalArgumentException 
      

      This only happens if the build picks up a change with a JIRA ID in the commit message.

      Reverting to 3.0.2, adding a new commit with a JIRA ID, and rerunning the build, is successsful, so this definitely seems to be something with 3.0.3 (alone or in combination with something else we're running).

      Attachments

        Issue Links

          Activity

            olamy Olivier Lamy added a comment -

            milkyman  what is the value you used? and what is the value of readTimeout?

            olamy Olivier Lamy added a comment - milkyman   what is the value you used? and what is the value of readTimeout?
            milkyman Horst Krause added a comment -

            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.

            milkyman Horst Krause added a comment - 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.
            olamy Olivier Lamy added a comment - - edited

            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 values

            I need to fix user help for this value

             

            olamy Olivier Lamy added a comment - - edited 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 values I need to fix user help for this value  
            medianick Nick Jones added a comment -

            olamy, 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.

            medianick Nick Jones added a comment - olamy , 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.
            medianick Nick Jones added a comment -

            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.

            medianick Nick Jones added a comment - 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.

            People

              olamy Olivier Lamy
              medianick Nick Jones
              Votes:
              10 Vote for this issue
              Watchers:
              27 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: