• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • influxdb-plugin
    • None
    • Jenkins 2.332.3
    • 3.2.1

      [InfluxDB Plugin] Collecting data... Error when executing always post condition: java.lang.ClassNotFoundException: hudson.tasks.test.AbstractTestResultAction at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1402) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1357) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1112) at java.base/java.lang.ClassLoader.loadClass(Unknown Source) Caused: java.lang.NoClassDefFoundError: hudson/tasks/test/AbstractTestResultAction at jenkinsci.plugins.influxdb.generators.JenkinsBasePointGenerator.hasTestResults(JenkinsBasePointGenerator.java:133) at jenkinsci.plugins.influxdb.generators.JenkinsBasePointGenerator.generate(JenkinsBasePointGenerator.java:108) at jenkinsci.plugins.influxdb.InfluxDbPublicationService.addPoints(InfluxDbPublicationService.java:335) at jenkinsci.plugins.influxdb.InfluxDbPublicationService.perform(InfluxDbPublicationService.java:179) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:226) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)

      Current workaround: Downgrade to 3.1.2

          [JENKINS-68573] Pipeline Error with influxdb-plugin v3.2

          Aleksi Simell added a comment -

          How are you calling InfluxDB plugin? I can't reproduce this issue, all my pipelines are passing normally with 3.2.

          Aleksi Simell added a comment - How are you calling InfluxDB plugin? I can't reproduce this issue, all my pipelines are passing normally with 3.2.

          Stephan Hohn added a comment -
              post {
                  always {
                      step([$class: 'InfluxDbPublisher', selectedTarget: 'influx.example.com'])
                      cleanWs()
                  }
          

          It's an InfluxDB v1.8

          Stephan Hohn added a comment - post { always { step([$class: 'InfluxDbPublisher' , selectedTarget: 'influx.example.com' ]) cleanWs() } It's an InfluxDB v1.8

          Aleksi Simell added a comment -

          Still cannot reproduce. What Jenkins version do you have? Did you update other plugins when you updated this one?

          Aleksi Simell added a comment - Still cannot reproduce. What Jenkins version do you have? Did you update other plugins when you updated this one?

          I have the same issue since I upgraded from 3.1.2 to 3.2.

          The plugin is only used via the global listener and no per-job configuration whatsoever is done.
          The attachment plugins.txt contains a list of the installed plugins.

          Andreas Nusser added a comment - I have the same issue since I upgraded from 3.1.2 to 3.2. The plugin is only used via the global listener and no per-job configuration whatsoever is done. The attachment plugins.txt contains a list of the installed plugins.

          Peter Loron added a comment - - edited

          We are also seeing this issue with jenkins 2.332.3 and influxdb 3.2. We use the global listener. This causes data to fail to be written to Influxdb.

          Peter Loron added a comment - - edited We are also seeing this issue with jenkins 2.332.3 and influxdb 3.2. We use the global listener. This causes data to fail to be written to Influxdb.

          Aleksi Simell added a comment -

          Could you verify that (based on JENKINS-27227) that enabling JUnit plugin doesn't resolve this issue?

          Aleksi Simell added a comment - Could you verify that (based on JENKINS-27227 ) that enabling JUnit plugin doesn't resolve this issue?

          The JUnit Plugin 1.63 was and is enabled. The problem is still there.

          Andreas Nusser added a comment - The JUnit Plugin 1.63 was and is enabled. The problem is still there.

          Aleksi Simell added a comment -

          I'm afraid I still cannot reproduce this issue. I didn't test with 2.332.3 version specifically, but I tested with 2.319 and 2.349 (latest) and both worked just fine.

          I did find that while cleaning the POM.xml for the 3.2 release, I accidentally removed JUnit plugin dependency taking it as a duplicate for the JUnit dependency. I re-added that in this PR. I'm now waiting for Jenkins checks to pass before merging that and then I'll probably make a quick 3.2.1 release that hopefully fixes this.

          Aleksi Simell added a comment - I'm afraid I still cannot reproduce this issue. I didn't test with 2.332.3 version specifically, but I tested with 2.319 and 2.349 (latest) and both worked just fine. I did find that while cleaning the POM.xml for the 3.2 release, I accidentally removed JUnit plugin dependency taking it as a duplicate for the JUnit dependency. I re-added that in this PR . I'm now waiting for Jenkins checks to pass before merging that and then I'll probably make a quick 3.2.1 release that hopefully fixes this.

          Aleksi Simell added a comment -

          3.2.1 released where some dependencies were fixed. Please try with new version and reopen if this doesn't resolve this issue.

          Aleksi Simell added a comment - 3.2.1 released where some dependencies were fixed. Please try with new version and reopen if this doesn't resolve this issue.

          Stephan Hohn added a comment -

          Can confirm 3.2.1 fixed my issue. Thanks for taking time solving it.

          Stephan Hohn added a comment - Can confirm 3.2.1 fixed my issue. Thanks for taking time solving it.

            aleksisimell Aleksi Simell
            mcsage Stephan Hohn
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: