• Type: New Feature
• Resolution: Unresolved
• Priority: Minor
• Component/s: xunit-plugin
• Labels:

  • plugin
  • xunit
• Environment:

  Windows
  Jenkins: 2.479.3
  Unit plugin: 3.1.5

[JENKINS-75165] When evaluating NUnit3 reports, warnings appear in the Jenkins log

Andreas Gallien created issue - 2025-01-18 19:00

Andreas Gallien made changes - 2025-01-18 19:00

Description

Original: When evaluating NUnit3 reports, warnings appear in the Jenkins log. We use the following evaluation: NUnit3(pattern: 'Logs/UnitTestResults/*_nunit.xml'),   This generates the warning: {noformat} Warning at function xunit:is-empty in line 51   SXWN9000 A function that calculates atomic values should use xsl:sequence and not xsl:value-of{noformat} It appears to be the xunit:is-empty function in XSLT. [https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/nunit-3.0-to-junit.xsl|http://example.com] {code:java}     <xsl:function name="xunit:is-empty" as="xs:boolean">         <xsl:param name="value" as="xs:string?" />         <xsl:value-of select="string($value) != ''" />     </xsl:function>{code}   Translated with DeepL.com (free version)

New: When evaluating NUnit3 reports, warnings appear in the Jenkins log. We use the following evaluation: NUnit3(pattern: 'Logs/UnitTestResults/*_nunit.xml'),   This generates the warning: {noformat} Warning at function xunit:is-empty in line 51   SXWN9000 A function that calculates atomic values should use xsl:sequence and not xsl:value-of{noformat} It appears to be the xunit:is-empty function in XSLT. [https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/nunit-3.0-to-junit.xsl|http://example.com/] {code:java}     <xsl:function name="xunit:is-empty" as="xs:boolean">         <xsl:param name="value" as="xs:string?" />         <xsl:value-of select="string($value) != ''" />     </xsl:function>{code}