[JIRA] [subversion-plugin] (JENKINS-29914) Subversion working copy is slow (low resolution timestamps?)

2016-01-04 Thread florent.fie...@siemens.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Florent Fievez commented on  JENKINS-29914 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion working copy is slow (low resolution timestamps?)  
 
 
 
 
 
 
 
 
 
 
Since the implementation of subversion client is done in SVNKit library, I think you should report the bug there.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [subversion-plugin] (JENKINS-29914) Subversion working copy is slow (low resolution timestamps?)

2015-08-12 Thread josh...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Kelley created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29914 
 
 
 
  Subversion working copy is slow (low resolution timestamps?)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 subversion-plugin 
 
 
 

Created:
 

 12/Aug/15 3:18 PM 
 
 
 

Environment:
 

 Jenkins 1.609.2, Subversion plugin 2.5, OpenJDK 7u79-2.5.6 (as provided by Ubuntu 14.04) 
 
 
 

Labels:
 

 performance subversion 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Josh Kelley 
 
 
 
 
 
 
 
 
 
 
Working copies created by the Jenkins Subversion plugin are very slow to work with. I think that the problem is that the plugin and its Subversion libraries don't maintain enough precision in file timestamps. 
Details: 
One of the steps in our build process runs svnversion on a large working copy. We noticed that this operation took over 30 times longer in a working copy created by Jenkins' Subversion plugin, compared to a working copy checked out in the standard svn command-line (CLI) client.