诊断 Cruise Control .NET 任务超时
我有一个运行良好的 CCNet 构建脚本，除了 MSBuild 任务偶尔会超时之外。我已经将超时从 600 增加到 900 到 1200。没有骰子，所以我相信这与 MSBuild 正在构建的内容有关；一个大型的旧 Web 应用程序项目。我已经在谷歌上查找过任何问题的迹象，但没有发现任何问题。
以前有人遇到过这个问题吗？更一般地说，您会采取哪些步骤来诊断 CCNet 中的超时？
I've got a CCNet build script that runs fine, with the exception of every now and then an MSBuild task times out. I've gone in and increased the timeouts from 600 to 900 to 1200. No dice, so I'm lead to believe it has something to do with what MSBuild is building; a big old web application project. I've looked on the google for any indication of issue here, but have turned up nothing.
Has anyone experienced this problem before? More generally, what steps do you take to diagnose a timeout in CCNet?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
尝试创建一个仅在命令行上运行 msbuild 项目的批处理文件，并使用 MsBuild Profiler 查看所有内容时间正在被花费。
良好的消除过程
Try creating a batch file that only runs the msbuild project on the command line and use MsBuild Profiler to see where all the time is being spent.
Good 'ol process of elimination
我也有类似的经历。在 cmd 提示符下调试并运行后，我发现问题出在写入权限上。
您应该检查输出文件夹指向的网络权限。通常Vista/Windows 7都有网络权限问题。
尝试授予输出文件夹完全权限，看看会发生什么。并尝试查看参考路径是否正确拾取。
从 VS 可以很好地构建，但是当您尝试从 CC.net 时，我们可能必须提供参考路径。
/p:ReferencePath=C:\Users...
希望这会有所帮助。
I had a similar experience. After debugging and running at cmd prompt I found out the issue was with the writing permissions.
You should check the Network permissions where the output folder is pointing to. Usually Vista/Windows 7 all have net work permission issues.
Try giving full permissions to the out put folder and see what happens. And also try to see Reference path is correctly picking up or not.
From VS it will build fine but when you try from CC.net we may have to give reference path.
/p:ReferencePath=C:\Users....
Hope this will be helpful.
我多次经历过类似的情况，本地构建速度相当快，但任务在巡航控制上超时。
它总是会从某个网络位置拉下东西（可能是代码的整个分支），并且巡航控制任务因此而超时。
其他选择，您建造的机器可能规格非常低，但您会注意到这一点！
I've experienced something similar a number of times where a local build was quite fast but the task was timing out on cruise control.
It always cooked down to pulling down stuff (maybe a whole branch of your code) from some network location and the cruise control task timing out for that reason.
Other option, you build machine could be very low on spec, but you would have noticed that!