哈德森离开公开会议
有人有过 Hudson 让会话向 Subversion 服务器开放的经历吗？
我们一直在增加我们的工作清单，并定期对 SCM 进行轮询，大约有 50 个工作清单。它一直工作正常，但最近我们的 SCM 开始拒绝握手，我们怀疑这归因于 Hudson 未开放的会话。
根据最新统计，大约有 400 个会话没有在 Hudson 上进行任何构建。目前我们找到的唯一解决方案是重新启动 Subversion 服务，但这变得越来越频繁，而且不是一个长期的解决方案。
任何经验/想法将不胜感激。
Does anyone have any experiences with Hudson leaving sessions open to a Subversion server?
We've been increasing our job list and got ~50 which poll the SCM regularly. It's been working fine but recently our SCM has started acting up by refusing handshakes, which we suspect is down to the sessions left open by Hudson.
Last count there were ~400 sessions with nothing building on Hudson. At the moment the only solution we've found is restarting the Subversion service but this is becoming increasingly frequent and not a long term solution.
Any experiences/ideas would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您是否经常重新启动 Hudson 服务器而不首先在“管理 Hudson”页面上执行“准备关闭”操作？服务器可能正在查询 Subversion 服务器，而某人只需停止并重新启动应用程序就可以使会话保持打开状态。
另外，您在工作中使用哪种 Subversion 身份验证方法？
Do you restart your Hudson server frequently without doing a Prepare for Shutdown on the Manage Hudson page first? It is possible the server could be in the middle of querying the Subversion server and someone simply stopping and restarting the app could leave sessions open.
Also, which Subversion Authentication method are you using for your jobs?