|
||||||||
|
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.
It seems that nowadays the solution to https://issues.jenkins-ci.org/browse/JENKINS-21785 also resolves this problem. i.e. Set addition credentials with the correct realm name format. e.g. <https://my-server-url.com:443> ID. You can find the correct authentication realm name by using "svn --no-auth-cache --config-dir invalid info https://my-server-url.com/trunk".
However this did not originally work for us. Not sure why it's working now. We upgraded the svn plugin to 2.5 then downgraded to 2.3. This may have had an impact. We also upgraded our version of Jenkins,
This defect can be marked as resolved.