[
https://issues.jenkins-ci.org/browse/JENKINS-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159340#comment-159340
]
Nick Boldt commented on JENKINS-12815:
--------------------------------------
It would also be nice to say that missing test coverage files (or empty ones)
should result in a warning (UNSTABLE) rather than an error (FAILED), or in some
cases be ignored entirely (STABLE).
+1 for being able to tweak the output colour/status of test & test coverage
failures to define them as less critical.
> 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
