Hudson 文件系统 SCM 是否“清除工作空间”？选项工作？
我正在尝试使用 Hudson 文件系统 SCM 来监视一个区域，并在它发生变化时启动构建。它在一个区域一直运行良好。我刚刚为其他区域添加了一项新工作，并告诉它“清理工作空间”。这似乎陷入了困境——我已经让构建不断排队，每个构建都声称找到了 2396 个新文件。该插件的文档表明这应该有效，而且我无法想象如果这不是我应该使用它的方式，他们为什么会提供该功能，但有什么想法是错误的吗？
I am trying to use Hudson filesystem SCM to monitor an area, and kick of a build when it changes. It has been working fine with one area. I have just added a new job for nother area, and told it to "clear workspace". This seems to go into a spin - I've had builds queued up continuously, each claiming to have found 2396 new files. The documentation for the plugin suggests this sould be working, and I can't imaging why they would have provided the feature if this is not how I am supposed to use it, but any ideas what is wrong?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我想我已经修好了。它每分钟轮询一次，但需要几分钟才能获取。我原以为在构建过程中轮询会暂停，但事实并非如此，因此下一次在 frechly 清除的文件夹中发现了许多丢失的文件。将轮询间隔设置为
似乎已经修复了它。
I think I have fixed it. It was polling every minute, but taking several minutes to fetch. I had expected that polling would be suspended while the build was under way, but it is not, so the next one along found lots of missing files in the frechly cleared folder. Setting the polling interval to
seems to have fixed it.