jenkinsci / jenkinsci/junit-plugin
[JENKINS-45883] how to mark build pass even if report generation fails
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 87
- Forks
- 351
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 2
Description
I have a job which has conditional run of tests which means if tests don't run there will be no xml file hence junit report plugin marks the build as FAILED. Even if I intentionally mark it SUCCESS using groovy post-build at the end, it doesn't work (weird)
A tick mark like feature, if selected while configuring job, will do help. I would like to contribute if this sounds a right option to have.
jenkins 2.62
junit plugin: 1.9
Originally reported by
pooja, imported from: how to mark build pass even if report generation fails
- status: Open
- priority: Minor
- component(s): junit-plugin
- label(s): junit-plugin, success
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 2025-11-26
Raw content of original issue
I have a job which has conditional run of tests which means if tests don't run there will be no xml file hence junit report plugin marks the build as FAILED. Even if I intentionally mark it SUCCESS using groovy post-build at the end, it doesn't work (weird)
A tick mark like feature, if selected while configuring job, will do help. I would like to contribute if this sounds a right option to have.
jenkins 2.62
junit plugin: 1.9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by examining how the junit-plugin handles a missing XML report and propagates the build result, then clarify the intended configuration behavior and verify that a job with no test report can remain successful when the option is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100