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

Reporting plugins report error on M2 project when one module doesn't have results

    XMLWordPrintable

Details

    Description

      after a successful build my result page shows the message "During parsing an error has been reported." for the Checkstyle, PMD and CPD plugin as well as the actual fixed/new warnings. When I click on the link [1] it says "No report files were found. Configuration error?" But the reports can be found as the warnings are correct.

      It is a multimodule maven project, which runs the pmd and checkstyle reports itself so that Hudson can pick up the results.

      I'm using a M2 job type and there is one module without results.

      Layout:

      /pom.xml <- aggregator pom, parent = released company pom
      /parent
      /parent/pom.xml <- parent pom, parent = released company pom
      /module-1
      /module-1/pom.xml <- module pom, parent = parent/pom.xml
      /module-2
      /module-2/pom.xml <- module pom, parent = parent/pom.xml

      The parent module doesn't contain any sources, so this doesn't contain any result files.

      Attachments

        Activity

          nick_stolwijk nick_stolwijk created issue -
          drulli Ulli Hafner made changes -
          Field Original Value New Value
          Component/s analysis-core [ 15709 ]
          Component/s checkstyle [ 15512 ]
          Component/s core [ 15593 ]
          Component/s plugin [ 15491 ]
          Component/s pmd [ 15511 ]
          Priority Major [ 3 ] Minor [ 4 ]
          drulli Ulli Hafner made changes -
          Description after a successful build my result page shows the message "During parsing an error has been reported." for the Checkstyle, PMD and CPD plugin as well as the actual fixed/new warnings. When I click on the link [1] it says "No report files were found. Configuration error?" But the reports can be found as the warnings are correct.

          It is a multimodule maven project, which runs the pmd and checkstyle reports itself so that Hudson can pick up the results.

          I'm using a M2 job type and there is one module without results.

          Layout:

          /pom.xml <- aggregator pom, parent = released company pom
          /parent
          /parent/pom.xml <- parent pom, parent = released company pom
          /module-1
          /module-1/pom.xml <- module pom, parent = parent/pom.xml
          /module-2
          /module-2/pom.xml <- module pom, parent = parent/pom.xml

          The parent module doesn't contain any sources, so this doesn't contain any result files.

          [1] http://localhost:8080/hudson/job/myproject/2463/checkstyleResult/error/
          after a successful build my result page shows the message "During parsing an error has been reported." for the Checkstyle, PMD and CPD plugin as well as the actual fixed/new warnings. When I click on the link [1] it says "No report files were found. Configuration error?" But the reports can be found as the warnings are correct.

          It is a multimodule maven project, which runs the pmd and checkstyle reports itself so that Hudson can pick up the results.

          I'm using a M2 job type and there is one module without results.

          Layout:

          /pom.xml <- aggregator pom, parent = released company pom
          /parent
          /parent/pom.xml <- parent pom, parent = released company pom
          /module-1
          /module-1/pom.xml <- module pom, parent = parent/pom.xml
          /module-2
          /module-2/pom.xml <- module pom, parent = parent/pom.xml

          The parent module doesn't contain any sources, so this doesn't contain any result files.
          drulli Ulli Hafner added a comment -

          Simple solution: skip parsing step for packaging 'pom'.

          drulli Ulli Hafner added a comment - Simple solution: skip parsing step for packaging 'pom'.
          drulli Ulli Hafner added a comment -

          Error messages should contain a reference to the maven module, if available.

          drulli Ulli Hafner added a comment - Error messages should contain a reference to the maven module, if available.
          oczkins oczkins added a comment -

          not only pom but any one that do not produce analisis report like 'ear' for example

          oczkins oczkins added a comment - not only pom but any one that do not produce analisis report like 'ear' for example

          Code changed in hudson
          User: : drulli
          Path:
          trunk/hudson/plugins/analysis-core/src/main/java/hudson/plugins/analysis/core/FilesParser.java
          http://jenkins-ci.org/commit/33226
          Log:
          [FIXED JENKINS-6895]: don't report an error in Maven projects if there is no analysis file to parse.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : drulli Path: trunk/hudson/plugins/analysis-core/src/main/java/hudson/plugins/analysis/core/FilesParser.java http://jenkins-ci.org/commit/33226 Log: [FIXED JENKINS-6895] : don't report an error in Maven projects if there is no analysis file to parse.
          scm_issue_link SCM/JIRA link daemon made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          drulli Ulli Hafner added a comment -

          Integrated in Hudson Plug-ins (Compile) #30
          [FIXED JENKINS-6895]: don't report an error in Maven projects if there is no analysis file to parse.

          drulli Ulli Hafner added a comment - Integrated in Hudson Plug-ins (Compile) #30 [FIXED JENKINS-6895] : don't report an error in Maven projects if there is no analysis file to parse.
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 136992 ] JNJira + In-Review [ 204322 ]

          People

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

            Dates

              Created:
              Updated:
              Resolved: