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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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?

            Assignee:
            sogabe
            Reporter:
            Greg Moncreaff
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: