jenkinsci / jenkinsci/junit-plugin

[JENKINS-7347] Hudson should support absolute paths for junit xml

Open
#879 3 comments 0 reactions 0 assignees View on GitHub
component:junit-plugin enhancement imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
87
Forks
351
Avg merge
1d 19h
Merged PRs (30d)
2

Description

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

---
Originally reported by sgrove, imported from: Hudson should support absolute paths for junit xml


  • status: Open
  • priority: Minor
  • component(s): junit-plugin
  • resolution: Unresolved
  • votes: 3
  • watchers: 4
  • imported: 2025-11-26

Raw content of original issue

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

  • environment: Ubuntu 10.04

1 attachment

- [hudson_01.png](https://issues.jenkins.io/secure/attachment/19702/hudson_01.png)
> ![hudson_01.png](https://issues.jenkins.io/secure/attachment/19702/hudson_01.png)

Contributor guide

Open the contributing guide

Research direction

Start by locating the junit-plugin code that reads and resolves JUnit XML report paths; the issue names no source file or test. Reproduce the reported absolute-path configuration and add coverage showing that results outside the workspace can be consumed, with the existing workspace-relative behavior still working.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.