jenkinsci / jenkinsci/junit-plugin

[JENKINS-3982] Option to quietly skip publisher if test reports do not exist

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

Description

Hi,

I've some trouble with the "Publish JUnit test result report" option. The fact

is that I've about 200 jobs to build my application. Some of them with junit

tests and others without. But no tests today doesn't mean no test tomorrow. My

problem is that the option doesn't check if the directory defined as the one

containing tests results exist or not. Then jobs without tests fail. Is there a

way to publish the reports only if the directory is existing or regarding the

value of a variable or...

Regards.

---
Originally reported by lahatch, imported from: Option to quietly skip publisher if test reports do not exist


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

Raw content of original issue

Hi,

I've some trouble with the "Publish JUnit test result report" option. The fact
is that I've about 200 jobs to build my application. Some of them with junit
tests and others without. But no tests today doesn't mean no test tomorrow. My
problem is that the option doesn't check if the directory defined as the one
containing tests results exist or not. Then jobs without tests fail. Is there a
way to publish the reports only if the directory is existing or regarding the
value of a variable or...

Regards.

  • environment: Platform: All, OS: All

Contributor guide

Open the contributing guide

Research direction

Start by locating the JUnit publisher implementation and its handling of a configured results directory. Reproduce a job with no JUnit reports, then verify the behavior when reports are present. Done means jobs without reports do not fail, while available reports are still published.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.