java - 由于 SVNAuthenticationException，Hudson 构建失败

Question

我在尝试使用 Hudson 构建项目时遇到意外错误。我有一个有效帐户，可以使用它结帐到安装了 Hudson 的机器。我已从 Hudson UI 更新了此帐户的身份验证参数。

有没有人遇到过这个？

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

Answer 1

我遇到了这个问题。在花了一天时间研究 ssl 和 http 交互之后，我发现这实际上是一个身份验证问题。

在 Jenkins v1.534

中的(加密)凭据

/opt/jenkins/jobs/JOBNAME/subversion.credentials

和

/opt/jenkins/hudson.scm.SubversionSCM.xml

已过时且不同步。为了让诊断变得更加困难，它们被缓存起来，并在我每次运行作业时被覆盖。因此，每次更改这些文件时，我都必须重新启动 jenkins 服务。