|
||||||||
|
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.
This is an issue tracker, not a support site. So when you're reporting an issue here, it needs to be relevant to the current state of the project. Otherwise developers spend effort trying to reproduce a problem (in this case that's quite a bit of effort, if possible at all given how little information you provide) that may have been fixed long ago. Subversion plugin 1.45 is obsolete since May 2013, Jenkins 1.534 unsupported since October 2014.
On the other hand, it shouldn't take you more than ten minutes to launch a current version of Jenkins on the affected machine (different port and Jenkins home of course), update SVN plugin to the current release, and confirm it still occurs with new versions in your environment. It makes the devs' job much easier without being a significant burden for you.
I'm not the only one with that view, see
JENKINS-26011for a similar example (it may also provide a hint as to what may be the problem here).To get assistance in resolving this problem, rather than report an issue, email the jenkinsci-users list, or ask in #jenkins on Freenode. Alternatively, contact one of the commercial Jenkins support vendors, such as Cloudbees, about a Jenkins support contract.