即使没有 Drops 文件夹，为什么我的 TFS 构建会浪费时间? [英] Why does my TFS build waste time eventhough there is no Drops folder?

问题描述

我们有一个 TFS 服务器 2013 的小型设置，并为单个项目运行构建.对于那个项目，我们只有一个关闭 Drops 功能的构建定义.也就是说，此构建不会将输出文件复制到放置文件夹.然而，我们每次保存构建定义时都会收到此消息:

We have a small setup of TFS server 2013 and running builds for a single project. For that project we only have a single build definition which has the Drops feature turned off. That is to say, This build does not copy output files to a drop folder. Yet we get this message every time we save the build definition:

此构建浪费时间和计算机资源，因为您的工作文件夹包括团队项目 (... Project)，其中包括一个滴文件夹.您应该隐藏 Drops 文件夹.看http://go.microsoft.com/fwlink/?LinkId=269693.

This build wastes time and computer resources because your working folders include the team projects (... Project), which include a Drops folder. You should cloak the Drops folders. See http://go.microsoft.com/fwlink/?LinkId=269693.

通常我会遵守并隐藏 Drops 文件夹.但这会导致构建在最后(在构建、测试和部署完成后)挂起，就在重置环境"之后.

Normally I would comply and cloak the Drops folder. But that causes the build to hang at the very end (after building, testing and deploying has been done), right after "Resetting environment".

我的问题是，为什么 TFS 警告我们必须隐藏 Drops 文件夹，即使实际上没有?还是在那里而我完全忽略了它?

My question is, why does TFS warn us about having to cloak the Drops folder even though there really isn't one? Or is there and I am overlooking it completely?

推荐答案

我遇到了同样的问题，上面的解决方案没有帮助，因为 Dylan Smith 没有解释如何在没有 Drops 文件夹(空或不为空)时停止警告)，这是原始问题中的问题.我的hack"解决方案是在根 TFS 项目中创建虚拟 Drops 文件夹并隐藏它.

I had the same problem and the solution above does not help since Dylan Smith does not explain how to stop the warning when there is no Drops folder (empty or not), which is the issue in the original question. My "hack" solution was to create dummy Drops folder in the root TFS project and cloak it.

这篇关于即使没有 Drops 文件夹，为什么我的 TFS 构建会浪费时间?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！