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

Warnings plugin gives exception since upgrading to Jenkins 1.588

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-plugin
    • None

      Since upgrading from Jenkins 1.584 to 1.588 and upgrading Warnings plugin from 4.42 to 4.43, I now see the following exception:

      [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
      ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
      java.lang.NoSuchMethodError: hudson.plugins.analysis.core.ParserResult.addAnnotations(Ljava/util/Collection;)V
      at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:405)
      at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:321)
      at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:319)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
      at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
      at hudson.model.Build$BuildExecution.post2(Build.java:183)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
      at hudson.model.Run.execute(Run.java:1784)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:89)
      at hudson.model.Executor.run(Executor.java:240)

          [JENKINS-25442] Warnings plugin gives exception since upgrading to Jenkins 1.588

          David Aldrich added a comment -

          I downgraded to Jenkins 1.584 and Warnings 4.42 and found that the exception still occurs. I upgraded quite a few other plugins when I upgraded to Warnings 4.43, so perhaps the problem is with one of those, but I don't know which one.

          David Aldrich added a comment - I downgraded to Jenkins 1.584 and Warnings 4.42 and found that the exception still occurs. I upgraded quite a few other plugins when I upgraded to Warnings 4.43, so perhaps the problem is with one of those, but I don't know which one.

          Same thing here!
          Please fix it!

          Balázs Baranyai added a comment - Same thing here! Please fix it!

          Daniel Beck added a comment - - edited

          As the linked issue indicates, you need to downgrade analysis-core ("Static Analysis" I think it's called) to 1.62, or upgrade to 1.65 if it exists already.

          Daniel Beck added a comment - - edited As the linked issue indicates, you need to downgrade analysis-core ("Static Analysis" I think it's called) to 1.62, or upgrade to 1.65 if it exists already.

          David Aldrich added a comment -

          Thanks, upgrading to Static Analysis plugin 1.65 fixed the problem.

          David Aldrich added a comment - Thanks, upgrading to Static Analysis plugin 1.65 fixed the problem.

            drulli Ulli Hafner
            davida2009 David Aldrich
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: