-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: junit-plugin
-
Labels:None
-
Environment:Ubuntu 10.04
-
Similar Issues:
Currently, hudson cannot consume junit xml output anywhere but a subdir of the workspace output
I have a job setup just executing a rake task that kicks off a bunch of spec tests. It's not in any scm, it's just setup to run every 15 minutes and hit a rake file. The rake file generates a series of junit xml at an absolute path, not anywhere near the project workspace, and no matter what I do with the junit xml path, hudson says it doesn't exist. I'm wondering if it's not possible to use absolute paths for the junit xml output
The ticket is old, but i've the same problem. I'm trying to use a workaround, to link (junction) the buildpath to the workspace, but this is an awful way 
I think the valid workaround for this would be to copy from the known path into the workspace using a bat/sh step. I don't think Jenkins should look outside the workspace path.
I have the same need for my project. At least the root of the fileset should be configurable to any path.