Jenkins 定期丢失工作空间，触发不需要的构建
我在 Jenkins 中设置了使用自定义工作区的构建（为了路径名中没有空格），使用 SCM (git) 轮询来检查更改。然而，似乎每隔 24 小时，我就会看到一个触发的构建，其中包含以下轮询日志：
Started on Jun 13, 2011 5:21:32 PM
No workspace is available, so can't check for updates.
Scheduling a new build to get a workspace.
Done. Took 1 ms
Changes found
它似乎只是为了获取工作区而安排构建（这是我明确不希望发生的事情），即使没有提交任何内容到 git。我取消了删除旧构建的选项，没有设置定期构建，并且每分钟使用一次 SCM 轮询。
我很困惑，无法提供比这更多的细节 - 除了我知道机器上存在工作区之外。除了实际提交到 git 之外，还有什么方法可以阻止这种情况发生吗？
I have builds set up in Jenkins that use custom workspaces (for the purpose of having no spaces in the path names), that use SCM (git) polling to check for changes. However, in what seems like exactly every 24 hours, I see a triggered build that has this polling log:
Started on Jun 13, 2011 5:21:32 PM
No workspace is available, so can't check for updates.
Scheduling a new build to get a workspace.
Done. Took 1 ms
Changes found
It appears to be scheduling a build simply to obtain a workspace (something I expressly do not want to happen) even though nothing has been committed to git. I have unticked the option to remove old builds, do not have a periodic build set up, and use SCM polling once a minute.
I'm stumped and can't provide more detail than this - other than I know the workspace exists on the machine. Is there any way to stop this from happening other than ACTUAL commits to git?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
版本 1.1.12 的 changelog 表明工作区不再需要进行轮询。升级到此版本的插件为我们解决了这个问题。
The changelog for version 1.1.12 indicates that a workspace is no longer required for polling. Upgrading to this version of the plugin fixed this problem for us.