Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12857

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: cobertura-plugin
    • Labels:
      None
    • Environment:
      rhel 5.5
    • Similar Issues:

      Description

      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?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sogabe sogabe
                Reporter:
                moncreaff Greg Moncreaff
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: