tigren zhang
closed JENKINS-14477 as Not A Defect
Build fails for svn revision check failed (403 Forbidden)
Problem solved, it is my fault, not the problem of Jenkins and plugin Subversion.
In fact, I ran a SVN command on Jenkins Master Server, so something in ~/.Subversion was changed. Then Jenkins updated the code with the wrong authentication.
I've deleted the folder ~/.Subversion, Jenkins has create new authentication now and works fine now.
By the way, I wonder why Jenkins use the authentication on Master? Shouldn't it use the authentication on slave only?
Thank you very much.
Change By:
tigren zhang
(23/Jul/12 1:38 AM)
Status:
InProgress
Closed
Resolution:
NotADefect
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