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

fail build if any empty files exist, or provide option to do it

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: xunit-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      Currently empty test results are just a warning, but it would be great if they could be configured as failures. In the case of phpunit, when it starts running, it creates an empty xml file. So if there is a fatal php error, it will just result in an empty, but new, file, and xUnit will happily warn but ignore this problem. For us it makes sense to always consider these errors, but maybe there should be a checkbox for "Fail the build if there are empty test files" or something.

      Attached is the patch we are using locally to accomplish this. Along with the previous patch, it makes our xUnit runs really robust and is the only way to ensure nothing is going wrong with the builds.

      Thanks for any comments!

        Attachments

          Activity

            People

            Assignee:
            gbois Gregory Boissinot
            Reporter:
            mcrooney mcrooney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: