[JENKINS-22747] Add Job Configuration Option to NOT fail JUnit Report publish when no test result files #30
Conversation
mistake - did not require this
…zero JUnit test reports generated Added field to track this Added logic around the condition
|
Oops!! |
jplandolt
changed the title
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
|
|
||
| /** | ||
| * @set the ignoreNoReports | ||
| * @since 1.596.2 |
There was a problem hiding this comment.
It's not the plugin's version. May be confusing
There was a problem hiding this comment.
What should the version number be used here, please?
…w constructors with signatures that will handle 'ignoreNoReports'
|
👍 for the contents. |
|
More or less same solution has been offered in pull-request #28, with the difference that the option is placed in "advanced" section and it provide unit tests to prove the functionality. |
|
Ok good to know! I'm happy to drop this request as soon as pull-request #28 is accepted. |
|
#28 has been accepted, so I will mark as closed. Thank you @jplandolt for working on this! |
|
And it's closed and the branch is in the wind. thanks :) |
Fix for JENKINS-22747. Allows the for each job to be configured so as to allow zero JUnit Result files. This is for projects that do not yet have any unit test results.
The default is false; jobs with zero JUnit Result files will fail the job. This is the current default behaviour of the plugin (as it should be)