[JIRA] (JENKINS-12857) cobertura - add option to make build as unstable (or not at all) instead of failed when no coverage xml files are found

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-12857) cobertura - add option to make build as unstable (or not at all) instead of failed when no coverage xml files are found

JIRA noreply@jenkins-ci.org
Greg Moncreaff created JENKINS-12857:
----------------------------------------

             Summary: cobertura - add option to make build as unstable (or not at all) instead of failed when no coverage xml files are found
                 Key: JENKINS-12857
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12857
             Project: Jenkins
          Issue Type: Bug
          Components: cobertura
         Environment: rhel 5.5
            Reporter: Greg Moncreaff
            Assignee: stephenconnolly


To be more graceful, consider an configuration option so the build isn't automatically marked as failed if no coverage files are found.

If you want visibility, you can always have some warning (exclamation point !) version of coverage icon on build landing page to say that 0 coverage files in anomalous situations.
and in normal ones you could report how many coverage files you found?

--
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

       
Loading...