[
https://issues.jenkins-ci.org/browse/JENKINS-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159276#comment-159276
]
Kohsuke Kawaguchi commented on JENKINS-12815:
---------------------------------------------
What I'm really trying to avoid in Jenkins is to have two dozen checkboxes and
text fields to cover every imaginable use case. Because Jenkins is a GUI tool
primarily, every such added switch has a real cost. In my humble opinion, this
feature falls on the wrong side of this trade-off.
I suppose what we can do is to define an extension point that abstracts away
the mapping from the test result into the result code. The config UI can be
smart enough not to show this option when no implementation is provided (and we
will not ship any in the junit plugin), and in this mode it can retain the
current behavior.
You can then develop an implementation of this extension point and achieve the
semantics you prefer.
> Add an option to select Build status when no Test is found
> ----------------------------------------------------------
>
> Key: JENKINS-12815
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12815
> Project: Jenkins
> Issue Type: New Feature
> Components: junit
> Affects Versions: current
> Environment: any
> Reporter: Mickael Istria
>
> Currently, when no test report is found by JUnit report plugin (ie fileset is
> empty), build fails.
> In some cases, this behaviour is too constraining and implies stopping a
> cascade of builds for example, and this is not always the mist convenient
> behavior for a build stack.
> This plugin should provide an option to select build status when fileset is
> empty:
> * FAILED (Red): current default behaviour
> * UNSTABLE (Orange)
> * STABLE (Blue/Green)
> This is an issue we have to build JBoss Tools, which we had to workaround by
> adding build steps, or adding dummy files to the fileset to avoid locking all
> builds in case of test failing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
