Make checking for modification time of junit results be configurable and off by default

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

XMLWordPrintable

    • 1119.va_a_5e9068da_d7

      The JUnit Result Archiver will fail the build if the test result files that match the filemask do not have a very recent modification time. The error message it prints is this:
      "Test reports were found but none of them are new. Did tests run?"

      This can be inconvenient in several settings; notably, when the clocks on the master and slave fall out of sync, or when the test results were generated by some process that isn't part of the build itself – maybe they were scp'd from somewhere else, for instance. Or for testing the JUnitResultArchiver itself.

      In my opinion, the behavior should be changed such that check-for-recent-modifications should be off by default. Additionally, the user should be able to specify a "recent" threshold via a setting.

            Assignee:
            Olivier Lamy
            Reporter:
            bshine
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: