[英]Hudson build fails due to SVNAuthenticationException
I am getting an unexpected error when trying to build a project with Hudson. 尝试使用Hudson构建项目时出现意外错误。 I have a valid account with which I can checkout to the machine on which Hudson is installed.
我有一个有效的帐户,我可以通过该帐户结账到安装了Hudson的机器。 I have updated from Hudson UI the authentication parameters to this account.
我已经从Hudson UI更新了此帐户的身份验证参数。
Has anyone else encountered this? 有人遇到过这种情况么?
hudson.util.IOException2: revision check failed on https://SVN Location
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:157)
at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:99)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:504)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:621)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1095)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1280)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:139)
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: OPTIONS of '/SVN Location': 403 Forbidden (https://SVN)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:610)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:273)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:261)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:516)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1001)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:178)
at org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482)
at org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:851)
at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:1016)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:891)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:823)
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:145)
... 10 more
I had this problem. 我有这个问题。 And after spending a day researching ssl and http interactions, I discovered that it was in fact an authentication problem.
在花了一天时间研究ssl和http交互后,我发现它实际上是一个身份验证问题。
in jenkins v1.534 the (encrypted) credentials in 在jenkins v1.534中的(加密)凭证
/opt/jenkins/jobs/JOBNAME/subversion.credentials
and 和
/opt/jenkins/hudson.scm.SubversionSCM.xml
Were out of date AND out of sync. 已过时且不同步。 And to make diagnosis more difficult they were cached, and overwritten every time I ran a job.
为了使诊断更加困难,他们被缓存,并在每次工作时都被覆盖。 So I had to restart the jenkins service every time I changed those files.
因此,每次更改这些文件时,我都必须重新启动jenkins服务。
Did you use the correct URL for SVN. 您是否使用了SVN的正确URL。 This is a common error when the capitalization is not correct.
当大小写不正确时,这是一个常见错误。 Maybe the URL is not SVN_Location but Svn_location
也许URL不是SVN_Location而是Svn_location
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.