[JENKINS-19223] Wrong timestamps for reverted files on update

When a reverted file is committed to svn, the updated Jenkins workspace will get the timestamp from the original file instead of the update time. This is a known issue in SVNKit and has already been fixed, see details at: http://issues.tmatesoft.com/issue/SVNKIT-322

The SVNKit version 1.7.6 that the subversion plugin is using is still affected by this bug. Because this is a major issue for any incremental build system that uses timestamps (and because I just spend a lot of time debugging this problem) I decided to duplicate the issue here.

---
Originally reported by tribe_tiki, imported from: Wrong timestamps for reverted files on update

• status: Open
  
• priority: Major
  
• component(s): subversion-plugin
  
• label(s): subversion, svn, timestamp
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

Raw content of original issue

When a reverted file is committed to svn, the updated Jenkins workspace will get the timestamp from the original file instead of the update time. This is a known issue in SVNKit and has already been fixed, see details at: http://issues.tmatesoft.com/issue/SVNKIT-322


The SVNKit version 1.7.6 that the subversion plugin is using is still affected by this bug. Because this is a major issue for any incremental build system that uses timestamps (and because I just spend a lot of time debugging this problem) I decided to duplicate the issue here.

• environment: Reproduced on Mac OSX, Linux and Windows slaves