-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Blocker
-
Component/s: jira-plugin
-
Environment:JIRA 3.0.3, Blue Ocean 1.9.0
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).
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
