Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Attachments: svn_trace.txt
Components: subversion
Created: 14/Jul/13 3:10 PM
Description:

I recently started migrating my projects from a subversion 1.6 server to a 1.7.9 server. Both use dav_svn through Apache. Since then, about 1 out of every 3 builds will fail with a "connection timed out" stack trace from the SVN plugin. This is happening with multiple projects, usually when getting an external. The new server should be substantially more performant than the old one, and is on a much faster network. If I move all the SCM tasks into scripts and use a "real" SVN 1.7 client, everything works reliably. Additionally, all my users have no trouble using the new server. Only Jenkins is failing. Full trace attached.

Project: Jenkins
Priority: Major Major
Reporter: Quentin Hartman
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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/groups/opt_out.
 
 

Reply via email to