Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: xunit-plugin
-
Labels:None
-
Environment:Jenkins LTS 1.596.3
xunit 1.100
-
Similar Issues:
Description
When using the Custom Tool option, it is mandatory to provide a custom stylesheet to convert unit tests results to Junit format.
By following the documentation, we stored the xsl file in $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl
And we configured the plugin with a custom tool stylesheet pointing to $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl
This is not working when building on a slave machine, as the path $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl is not relevant on a slave (only for the master)
What about supporting URL instead, so using $JENKINS_URL/userContent/cunit/cunit-to-junit.xsl could work.
Attachments
Issue Links
- is blocking
-
JENKINS-52392 Support custom junit format that does not respect any precise schema
-
- Resolved
-
Since 2.0.3 If you use the Custom Tool optional you can place the XSL file where you want on master or in workspace.
By default it try to lookup the file path you provided against master node and than locally to workspace (that could be on slave). So it work with same file path regardless of slave or not. Since 2.0.5 the path could be specific also for a slave node.
Even more in your specific case seems you would override the CUnit XSL, since 2.0.3 is sufficent place custom XSL as documented in the "<jenkins_home>/userContent/cunit/<version_present>cunit-to-junit.xsl" and keep the "CUnit" as configured tool, you do not need swith con "Custom Tool". XUnit will read the file from master userContent also when build is on slave.