Hi,

@slawek Chaining the timestamp with touch is a workaround not a solution.

In my opinion the best solution is to make this check configurable with 2 parameters, one configuration parameter to indicate if enable or disable and the second one if enable to indicate the maximal allowed timestamp difference.

Mariano.-

I agree with mcerdeiro on the solution.

I'm facing this issue when the code was not changed only configuration files that are not affecting the test.

+1 for Mariano Cerdeiro's suggested solution. We've got builds failing because of 5 second differences.

Gradle 4.0 moved build cache from incubating state to production. Build cache among other things caches JUnit test results, which results in continuous failures. It actually blocks our implementation of pipelines.

I'm also blocked by this – I use a single Jenkins pipeline job to execute tests (across multiple environments – we want reporting on a per-environment level), and then another job executes which pulls those JUnit results into the workspace, and builds a report. I am encountering this on XMLs that are ~5 seconds "old".

This Powershell script works, but still not the greatest:

$files = Get-ChildItem "${WORKSPACE}"
  foreach ($i in $files) {
  $i.LastWriteTime = $(Get-Date)
}

Echoing what alex_dubrouski said, this totally breaks incremental builds from tools like Gradle.

Is there any progress on this? We are also hit by this, so currently we have only the option to disable junit recording at all...

This one is nine (9) years old. Come on, please fix this!

Note: I filed this too on GitHub which is related https://github.com/jenkinsci/junit-plugin/issues/201

Fixed in jenkinsci/junit-plugin#384. Released in 1119.va_a_5e9068da_d7.