jenkinsci / jenkinsci/junit-plugin

[JENKINS-43473] Add support for hostname attribute in Junit XML

Open
#1,072 1 comment 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

JUnit XML has a hostname attribute as part of testsuite element. At least in a number of schemas I found.

Adding support for this attribute would allow us:



  1. Possibly displaying it along with the testcase or testsuite results.

  2. Would make deduplication easier for parallel jobs or same tests running on diff machines/architectures/operating systems.

  3. Since a different slave could be used for a different test run would make it easier to see how results vary if we can tell which slave was used to run the tests.

---
Originally reported by gena01, imported from: Add support for hostname attribute in Junit XML


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

Raw content of original issue

JUnit XML has a hostname attribute as part of testsuite element. At least in a number of schemas I found.

Adding support for this attribute would allow us:



  1. Possibly displaying it along with the testcase or testsuite results.

  2. Would make deduplication easier for parallel jobs or same tests running on diff machines/architectures/operating systems.

  3. Since a different slave could be used for a different test run would make it easier to see how results vary if we can tell which slave was used to run the tests.


Contributor guide

Open the contributing guide

Research direction

The issue names the junit-plugin component and the JUnit XML testsuite hostname attribute, but no files, tests, or entry points. Start by locating where JUnit XML is parsed and results are represented; done requires an agreed way to retain and expose hostname, including its role in deduplication.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
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.