[JENKINS-2734] JUnit reports - setting threshold of failed tests to mark build as stable/unstable/failed

I would like to set maximum number of junit tests which can fail

during build and the build is marked still as stable, as unstable or as failed.

I found this option in task plugin, compiler warnings plugin etc. but

not in jUnit reports.

see configuration section of Task Scanner plugin

http://hudson.gotdns.com/wiki/display/JENKINS/Task+Scanner+Plugin

and/or Warnings plugin http://hudson.gotdns.com/wiki/display/JENKINS/Warnings+Plugin

---
Originally reported by ondraz, imported from: JUnit reports - setting threshold of failed tests to mark build as stable/unstable/failed

• assignee: timja
  
• status: Open
  
• priority: Major
  
• component(s): junit-plugin
  
• resolution: Unresolved
  
• votes: 35
  
• watchers: 29
  
• imported: 2025-11-26
  

I would like to set maximum number of junit tests which can fail

during build and the build is marked still as stable, as unstable or as failed.


I found this option in task plugin, compiler warnings plugin etc. but

not in jUnit reports.


see configuration section of Task Scanner plugin

http://hudson.gotdns.com/wiki/display/JENKINS/Task+Scanner+Plugin


and/or Warnings plugin http://hudson.gotdns.com/wiki/display/JENKINS/Warnings+Plugin

• environment: Platform: All, OS: All

No files, tests, or entry points are named. Start by locating the JUnit report publication and build-status configuration, then compare the threshold configuration in the referenced Task Scanner or Warnings plugins; done means users can configure failed-test limits that mark builds stable, unstable, or failed.

Written by the indexing model from the issue text.