|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I have this problem now, too. I'm using svn+ssh:// with private key. The dangling connections/dangling svnserve processes are seemingly produced by concurrent svn accesses, ie. a revision check by jenkins blocked by a manual svn commit. I'm also using the svn post-commit hook to trigger project rebuilds, so the likelyhood of jenkins getting into conflict with commits is rather high. When I do NOT do anything as a regular user with the repository, the problem seems to not exist...