如何为 hudson (jenkins) 持续集成系统正确配置 SVN? [英] How to correctly configure SVN for hudson (jenkins) continous integration system?

查看:27
本文介绍了如何为 hudson (jenkins) 持续集成系统正确配置 SVN?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在配置 jenkins 以在 MacOS 10.6.6 上构建我的 XCode 项目.为此,我安装了最新的 tomcat 容器和最新的 jenkins 作为 ROOT.war.除了添加 subversion 集成外,一切正常:(.在 jenkins 中创建一个新项目后,我在源代码管理"中选择了subversion",并以我在命令行 subversion 工具中使用的相同方式输入了我的存储库 URL:

I'm configuring a jenkins to build my XCode project on MacOS 10.6.6. For this purpose i have installed latest tomcat container and latest jenkins as ROOT.war. All works fine except adding subversion integration :(. After creating a new project in jenkins i selected "subversion" in "Source Code Management" and entered my repository URL same way i use in command-line subversion tool:

https://svn.mydomain.local/main/project/trunk

不幸的是,它无法处理奇怪的错误身份验证已取消":

Unfortunately, it is not working with a strange error "authentication cancelled":

详细信息"日志如下所示:

The 'details' log looks like this:

Unable to access https://svn.mydomain.local/main/project/trunk : svn: authentication cancelled 
org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
    at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)
    at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getNextAuthentication(DefaultSVNAuthenticationManager.java:257)
    at hudson.scm.FilterSVNAuthenticationManager.getNextAuthentication(FilterSVNAuthenticationManager.java:39)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:552)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:275)
    at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:263)
    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.testConnection(DAVRepository.java:97)
    at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:1842)

最奇怪的事情:如果我单击输入凭据"并输入我的登录名和密码,Jenkins 会报告身份验证成功.信息现在存储在 Hudson 中."但它仍然是红色的无法访问"和构建时的结帐错误:(.

The most strange thing: if i click "enter credentials" and enter my login and password, Jenkins reports back "Authentication was successful. Information is stored in Hudson now." but it's still red "unable to access" and checkout error on build :(.

命令行 svn co 适用于用户和 root 帐户并缓存所有凭据.也许任何对 macos 有过 hudson 经验的人都可以给出一些提示?

Command-line svn co works fine for both user and root accounts with all credentials cached. Maybe anyone who has a hudson on macos experience can drop a few hints what to do?

推荐答案

只是为了检查基本设置,运行 tomcat/jenkins 的用户是否具有对 .hudson 目录及以下目录的写访问权限,特别是对 hudson.scm.SubversionSCM.xml?

Just to check the basic setup, does the user running tomcat/jenkins have write access to the .hudson directory and below, specifically to hudson.scm.SubversionSCM.xml?

此外,其他人 在 JAVA_ARGS 中设置 -Dsvnkit.http.methods=Basic,NTLM 成功.

Additionally, someone else had success with setting -Dsvnkit.http.methods=Basic,NTLM in the JAVA_ARGS.

这篇关于如何为 hudson (jenkins) 持续集成系统正确配置 SVN?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆