|
||||||||
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/d/optout.
Thanks a lot!
Actually, I upgraded Jenkins to 1.580 two days ago (because of the SVN trouble, I preferred to stick with the stable versions). And it seems that the problem is now "gone" ... or at least, in the state as described above, meaning it does occur but not recur, which seems heavenly after many many weeks of pain.
Just for the record, I logged all outgoing Jenkins connections to SVN, namely svnkit-network and hudson.scm.CredentialsSVNAuthenticationProviderImpl, but I couldn't find anything unusual.
Welp. Seems there is no explanation, but at least a solution!