Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: xunit-plugin
    • Labels:
    • Environment:
      linux kernel 3.2.1
      boost 1.46
      jenkins 1.454
      xunit plugin 1.40
    • Similar Issues:

      Description

      Hello,

      I am trying to connect ourg UnitTest system with Jenkins using xunit plugin.
      The boost xml file is generated by using the following command-line parameters:
      --log_level=all --output_format=XML --report_level=no

      Giving the output to jenkins gives:
      ... .xml' for the metric 'BoostTest' is not valid. The result file has been skipped.

      Is there any possibility to validate against the Boost-Test xsd manually? To investigate the problem. I searched for a XSD file but could not find any file nor reference.

      I also tried to find some uUnit output using the Logger mechanism. The description on the plugin website does not work
      and also did not look as it could work because the build-in help tells a different syntax. So I tried several Logger like (setting priority to 'all'):
      com.thalesgroup.hudson.plugins.xunit.service.XUnitService
      com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer
      com.thalesgroup.hudson.plugins.xunit.service.XUnitValidationService
      com.thalesgroup.hudson.plugins.xunit.service.XUnitReportProcessorService
      com.thalesgroup.hudson.plugins.xunit.service.XUnitLog
      xUnit

      But the xUnit Logger stayed empty.

      So sadly I could not provide any debug information, despite the log file.

      Regards,
      Matthias Scholz

        Attachments

          Activity

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              matthiasscholz Matthias Scholz
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: