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

Task-scanner plugin, CPD plugin fail to produce reports

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • tasks-plugin
    • None
    • Platform: All, OS: All

      The task-scanner plugin and CPD plugin fail to produce reports when I have the
      following other post-build actions enabled, even though they are both correctly
      configured:

      • Publish Javadoc
      • Publish JUnit test result report
      • Record Emma coverage report
      • Publish FindBugs analysis results
      • Publish PMD analysis results
      • Publish Java NCSS Report
      • Editable Email Notification (Email-ext)

      All of these others work as expected. The task-scanner and CPD plugins don't
      seem to be invoked at all, since the console log ends with something like the
      following:

      BUILD FAILED
      /var/hudson/jobs/MyProject/workspace/project/build/eclipse/build-main.xml:41:
      Tests failed

      Total time: 6 minutes 26 seconds
      Publishing Javadoc
      Recording test results
      Recording Emma reports
      project/target/pluginbuilder/buildDirectory/results/testresults/coverage/coverage.xml
      Email was triggered for: Failure
      There are 1 triggered emails.
      Sending email for trigger: Failure
      Sending e-mails to: mail@example.com
      Finished: FAILURE

      I have tried disabling the Email-ext notification, but this doesn't make any
      difference.

          [JENKINS-3552] Task-scanner plugin, CPD plugin fail to produce reports

          f_copperfield added a comment -

          I now noticed that only the Emma coverage and Java NCSS report were shown in the
          scenario described. Therefore the following plugins do not produce any output
          currently:

          • FindBugs
          • PMD
          • Task-scanner
          • CPD

          f_copperfield added a comment - I now noticed that only the Emma coverage and Java NCSS report were shown in the scenario described. Therefore the following plugins do not produce any output currently: FindBugs PMD Task-scanner CPD

          Ulli Hafner added a comment -

          All of my plug-ins are not invoked for FAILED builds, this is by intention. You
          need to change your ant build.xml so that it does not fail the build for broken
          tests. Hudson will then automatically set the build status to UNSTABLE.

          Ulli Hafner added a comment - All of my plug-ins are not invoked for FAILED builds, this is by intention. You need to change your ant build.xml so that it does not fail the build for broken tests. Hudson will then automatically set the build status to UNSTABLE.

          f_copperfield added a comment -

          I now see that there is a distinction in Hudson between unstable and failed
          builds, so will attempt to configure my setup so that the build is marked
          unstable when tests fail, not as unsuccessful. Then your plugins will happily
          run. Please add to the documentation that the plugins do not run for FAILED builds.

          f_copperfield added a comment - I now see that there is a distinction in Hudson between unstable and failed builds, so will attempt to configure my setup so that the build is marked unstable when tests fail, not as unsuccessful. Then your plugins will happily run. Please add to the documentation that the plugins do not run for FAILED builds.

            drulli Ulli Hafner
            f_copperfield f_copperfield
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: