subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: Timestamp issue with "svn status" in 1.9.3
Date Thu, 08 Sep 2016 17:29:49 GMT
On Thu, Sep 08, 2016 at 07:40:24AM -0700, xvdessel@gmail.com wrote:
> I believe the timestamp to have a granularity of minutes on Linux, but I'm 
> not sure of this. Even if it has second precision, such merge scripts can 
> beat that.

This depends on the file system being used. Microseconds are not uncommon.

> In bash code, we can easily add the use-commit-times option. But when using 
> the SVN plugin in Jenkins, you cannot pass extra options like this one 
> unless you change de default settings of the account.

There is a --config-option command line option which can pass any config
file option on the command line without requiring changes to files on disk.
You should be able to force the use-commit-times option like this:

 svn --config-option config:miscellany:use-commit-times=yes

This option exists in Apache Subversion. The Jenkins plugin uses SVNKit which
is a reimplementation of Subversion written in Java, so it might not work.
The options are usually compatible, though, so it's worth a try.

Mime
View raw message