问题描述
这种情况不断发生，然后在多个Jenkins工作中全天随机解决:
This keeps on happening and then resolving itself randomly throughout the day, across multiple Jenkins jobs:
hudson.util.IOException2: revision check failed on http://svn.myCompanyRepo.com/path/to/project
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189)
at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:738)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:899)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580)
at hudson.model.Run.execute(Run.java:1676)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: org.tmatesoft.svn.core.SVNCancelException: [etc...]
有没有其他人遇到过这种情况，有没有简单的解决方法?我已经厌倦了收到有关这些错误错误的电子邮件.
Has anyone else been experiencing this and is there an easy fix? I'm getting tired of getting emails for these false errors.
(不幸的是)我们的Jenkins环境位于Windows Server 2008 R2虚拟机上.
Our Jenkins environment is on (unfortunately) a Windows Server 2008 R2 virtual machine.
推荐答案
使用svnkit看起来像是一个错误.您正在使用哪个版本的SVN插件?什么时候开始发生?您可以使用Subversion URL在服务器上进行结帐吗?
This looks like an error using svnkit. What version of the SVN plugin are you using? When did this start happening? Can you do a checkout on your server using the Subversion URL?
这就是我要做的:
- 在您的 Windows Server 2008 R2虚拟机上，安装Subversion命令行客户端(如果尚未安装的话).
- 在该构建系统上，禁用出现错误的构建.这样，在调试问题时就不会在您身上构建它.
- 使用控制台找到正在检出该作业的工作目录.尝试自己在那里进行结帐.
- 如果您无法进行结帐，但又遇到其他错误，则可能是网络方面的问题.
- 如果您可以从该服务器进行签出，则问题可能出在Subversion插件版本上.尝试将插件移回该插件的先前版本.现在，它是2.2(适用于我).我可以降级到的先前版本是1.54.
- On your Windows Server 2008 R2 virtual machine, install the Subversion command line client, if one isn't already installed.
- On that build system, disable the build that's having the error. This way, it doesn't get built on you while you're debugging what's wrong.
- Using the console, find the work directory where that job is being checked out. Try to do a checkout there yourself.
- If you can't do a checkout, but get some other error, it's possible that there's a network issue involved.
- If you can do a checkout from that server, then the problem might be the Subversion plugin version. Try to move the plugin back to the previous version of that plugin. Right now, it's at 2.2 (which works for me). The previous version I can downgrade to is 1.54.
运行Jenkins的用户是谁?我知道在Windows上，它可能是一个服务帐户，这使得调试这些东西变得很困难.我通常将其更改为我可以登录的名为"Jenkins"的用户.这样，我就是运行Jenkins的同一用户.
Who is the user who runs Jenkins? I know on Windows, it can be a service account which makes it hard to debug these things. I usually change that to a user called "Jenkins" I can log in as. This way, I'm the same user that's running Jenkins.
看看这是否可以帮助您解决问题.
See if this helps you pin down the issue.
这篇关于Jenkins始终使用hudson.util.IOException2失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！