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

Pipeline Maven Integration plugin fails with FindbugsAnalysisPublisher is missing its descriptor exception

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • pipeline-maven-plugin
    • None
    • Jenkins version: 2.492.3
      Pipeline Maven Integration plugin version: 1567.vb_2c3a_2116860

      Hi team. I updated the pipeline maven integration plugin from version 1508.v347c4b_692202 to 1567.vb_2c3a_2116860 and our builds started fail with an error:
      org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 37fc4de5-73c5-47ea-944d-664a08a0399b
      java.lang.AssertionError: class org.jenkinsci.plugins.pipeline.maven.publishers.FindbugsAnalysisPublisher is missing its descriptor
      at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1554)
      at hudson.model.AbstractDescribableImpl.getDescriptor(AbstractDescribableImpl.java:43)
      at PluginClassLoader for pipeline-maven//org.jenkinsci.plugins.pipeline.maven.MavenPublisher.getDescriptor(MavenPublisher.java:47)
      at PluginClassLoader for pipeline-maven//org.jenkinsci.plugins.pipeline.maven.MavenPublisherStrategy$1.buildPublishersList(MavenPublisherStrategy.java:66)
      at PluginClassLoader for pipeline-maven//org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:144)
      at PluginClassLoader for pipeline-maven//org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution2$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution2.java:1365)
      at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:141)
      at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77)
      at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
      at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
      at java.base/java.lang.Thread.run(Thread.java:840)
      We have no findbugs plugin installed, but com.google.code.findbugs maven plugin's used. We do not really need finbugs report published in Jenkins, so previously plugin was just showing warning messages:
      16:24:18 Recording test results*16:24:26* [Checks API] No suitable checks publisher found.16:24:27 [withMaven] Jenkins FindBugs Plugin not found, don't display org.codehaus.mojo:findbugs-maven-plugin:findbugs results in pipeline screen.16:24:27 [withMaven] jgivenPublisher - Jenkins JGiven Plugin not found, do not archive jgiven reports.16:24:27 [withMaven] Jenkins Task Scanner Plugin not found, don't display results of source code scanning for 'TODO' and 'FIXME' in pipeline screen.16:24:27 [withMaven] Publishers: Pipeline Graph Publisher: 40 ms, Invoker Publisher: 4 ms, Junit Publisher: 8114 ms, Concordion Publisher: 2 ms, Dependencies Fingerprint Publisher: 799 ms, Findbugs Publisher: 1 ms, JGiven Publisher: 1 ms, SpotBugs Publisher: 1 ms, Open Task Scanner Publisher: 1 ms*16:24:27* [withMaven] JacocoPublisher is no longer implicitly used with `withMaven` step.16:24:27 [withMaven] Jacoco plugin has been deprecated and should not be used anymore.16:24:27 [withMaven] Usage of Coverage plugin is recommended.16:24:27 [withMaven] See https://plugins.jenkins.io/coverage/#plugin-content-pipeline-example.
      Rolling back to the version 1567.vb_2c3a_2116860 fixed an issue.

            Unassigned Unassigned
            denys_mazhar_quant Denys
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: