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

Jira plugin: NoSuchMethodError: hudson.plugins.jira.JiraBuildAction.<init>(Lhudson/model/Run;Ljava/util/Set;)

XMLWordPrintable

      After upgrading jira-steps-plugin to 1.6.0 (also using latest blue ocean), the following exception occurs when using a jira step inside a workflow:

       java.lang.NoSuchMethodError: hudson.plugins.jira.JiraBuildAction.<init>(Lhudson/model/Run;Ljava/util/Set;)V
17:28:43  	at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:64)
17:28:43  	at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:876)
17:28:43  	at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1000(WorkflowRun.java:137)
17:28:43  	at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1168)
17:28:43  	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:150)
17:28:43  	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)
17:28:43  	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)
17:28:43  	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
17:28:43  	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
17:28:43  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
17:28:43  	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
17:28:43  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
17:28:43  	at java.lang.Thread.run(Thread.java:748)

      rolling back jira-steps-plugin to 1.5.5 seems to fix the issue

          [JENKINS-64148] Jira plugin: NoSuchMethodError: hudson.plugins.jira.JiraBuildAction.<init>(Lhudson/model/Run;Ljava/util/Set;)

          Fabian Holler added a comment - - edited

          We have builds failing with the same error message but we do not have the jira-steps plugin installed.
          We have the "jira" (v. 3.1.2) and the "jira-blueocean" (v. 1.24.32 plugin installed though. Our  jenkins version is 2.264

          When I retrigger a job that failed with this issue, all restarted builds succeeded so far. (wrong)

           

          Update: Downgrading the Jira plugin to version 3.1.1 seem to have solved the issue.
          It might have been introduced with https://github.com/jenkinsci/jira-plugin/pull/283

           

           

          Fabian Holler added a comment - - edited We have builds failing with the same error message but we do not have the jira-steps plugin installed. We have the "jira" (v. 3.1.2) and the "jira-blueocean" (v. 1.24.32 plugin installed though. Our  jenkins version is 2.264 When I retrigger a job that failed with this issue, all restarted builds succeeded so far. (wrong)   Update: Downgrading the Jira plugin to version 3.1.1 seem to have solved the issue. It might have been introduced with https://github.com/jenkinsci/jira-plugin/pull/283    

          Juan Pablo Santos Rodríguez added a comment -

          Hi, after downgrading jira-steps-plugin we're still seeing the same stacktrace. Upon further examination, we came to the same conclusion as fho, seems that downgrading jira-plugin to 3.1.1 does the trick, will update the issue to reflect that.

          Juan Pablo Santos Rodríguez added a comment - Hi, after downgrading jira-steps-plugin we're still seeing the same stacktrace. Upon further examination, we came to the same conclusion as fho , seems that downgrading jira-plugin to 3.1.1 does the trick, will update the issue to reflect that.

          Zhenlei Huang added a comment - - edited

          Cross link github PR https://github.com/jenkinsci/jira-plugin/pull/299.

          Zhenlei Huang added a comment - - edited Cross link github PR  https://github.com/jenkinsci/jira-plugin/pull/299 .

          Patrik Schalin added a comment -

          Hi,

          Also seeing this problem when upgraded to 2.265 and Jira plugin 3.1.2.

          Downgrade Jira plugin to 3.1.1 seems to solve it for us too.

          Patrik Schalin added a comment - Hi, Also seeing this problem when upgraded to 2.265 and Jira plugin 3.1.2. Downgrade Jira plugin to 3.1.1 seems to solve it for us too.

          Fabian Holler added a comment -

          Thanks a lot for the fast response, gmshake!

          Fabian Holler added a comment - Thanks a lot for the fast response, gmshake !

          Zhenlei Huang added a comment -

          Hi,

          jira-plugin version 3.1.3 has been released, but there may be some delay on the update center. The release note:  https://github.com/jenkinsci/jira-plugin/releases/tag/jira-3.1.3

          Zhenlei Huang added a comment - Hi, jira-plugin version 3.1.3 has been released, but there may be some delay on the update center. The release note:   https://github.com/jenkinsci/jira-plugin/releases/tag/jira-3.1.3

          Mark Waite added a comment -

          Thanks gmshake. It is quite a delight to detect a failure in a job and discover that others have already detected it, the maintainer has resolved it, and a new plugin is released with the fix. My sincere thanks for your rapid response to the issue!

          Mark Waite added a comment - Thanks gmshake . It is quite a delight to detect a failure in a job and discover that others have already detected it, the maintainer has resolved it, and a new plugin is released with the fix. My sincere thanks for your rapid response to the issue!

            gmshake Zhenlei Huang
            juanpablo Juan Pablo Santos Rodríguez
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: