[JENKINS-5901] Allow to obtain JUnit XML files through HTTP

See complete mail thread at http://n4.nabble.com/Getting-junitResult-xml-through-HTTP-td1583391.html.

[Abstract]

It'd be cool if a Hudson IDE client could load failed tests into the IDE's JUnit window/plugin/etc. For that to happen the client would need access to the JUnit XML files generated by surefire.

[Which files?]

My idea is to simply make the JUnit XML files in the workspace available. Two aggregate actions could provide

• a set of files for all failed tests OR


• a set of all JUnit XML files
  
  Alternatively, a client should be able to retrieve a single file through HTTP if he only needs a specific file. That use case is IMO of lower relevance, though.

[Kohsuke's input]

...from mailing list...sorry, didn't quite get it...

"I think it'd be nice to add an XML API for those test reports that fake

the canonical JUnit XML format. That would allow all the existing test

frameworks to expose its results to other programs.

Either that or we should change the JUnit report plugin to keep the

original report XML files, but the problem is that they can be separated

into many files and it's not easy for others to programmatically access

them in a reliable way."

---
Originally reported by marcelstoer, imported from: Allow to obtain JUnit XML files through HTTP

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

See complete mail thread at http://n4.nabble.com/Getting-junitResult-xml-through-HTTP-td1583391.html.


[Abstract]

It'd be cool if a Hudson IDE client could load failed tests into the IDE's JUnit window/plugin/etc. For that to happen the client would need access to the JUnit XML files generated by surefire.


[Which files?]

My idea is to simply make the JUnit XML files in the workspace available. Two aggregate actions could provide



	
a set of files for all failed tests OR

	
a set of all JUnit XML files

Alternatively, a client should be able to retrieve a single file through HTTP if he only needs a specific file. That use case is IMO of lower relevance, though.



[Kohsuke's input]

...from mailing list...sorry, didn't quite get it...

"I think it'd be nice to add an XML API for those test reports that fake

the canonical JUnit XML format. That would allow all the existing test

frameworks to expose its results to other programs.


Either that or we should change the JUnit report plugin to keep the

original report XML files, but the problem is that they can be separated

into many files and it's not easy for others to programmatically access

them in a reliable way."

No source files, tests, or entry points are named. Start by reviewing the junit-plugin handling of Surefire-generated JUnit XML and the existing HTTP/API extension points; define whether completion means aggregate failed reports, all reports, or individual-file retrieval, then add coverage for the chosen behavior.

Written by the indexing model from the issue text.