-
Bug
-
Resolution: Not A Defect
-
Major
-
Jenkins 1.447.1 on Windows Server 2008, Tomcat 6.0.12
Plugin Subversion 1.34
We encouter a problem since last Friday that many jobs could not build because of svn update failed.
The problem is familar with this one: http://jenkins.361315.n4.nabble.com/build-fails-for-svn-revision-check-td380508.html
Details:
Some jobs don't allow anonymous access to SVN, username and password is required.
1. Configure
When configure the job, we fill the Subversion blank, but it says "Unable to access https://svn_url/svn/asa_w2w/trunk : svn: OPTIONS /svn/asa_w2w/trunk failed (show details)
(Maybe you need to enter credential?) ".
But after we click the "enter credential" and input right username and password, the error is still there.
You can see it in the image attachment.
2. Build
- If a build is triggered with no changes in svn repository then it works fine with no error.
- If a build is triggered because of change in repository caught by poller then it gives revision check error (403 Forbidden) and fails
- If the build fails because of the svn revision check the next build passes as long as there are no repository changes.
SVN works well in local machine, we can check out, update and commit normally.
We have tried to delete the content in ~/.Subversion of slave machine, but nothing good happened.
This problem is so weird that the related jobs worked fine before last Friday and we did not make any change to Jenkins last Friday.
I attach the build log and Jenkins log, hope it useful for you, Thanks.