调试由MSBuild排队的构建 [英] Debugging a build queued by MSBuild

查看:86
本文介绍了调试由MSBuild排队的构建的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

 我们已经使用msbuild配置了构建,并且可以在276个项目中运行.现在,如果一个项目在两个小时后失败,则说175号项目无法编译,则MSBuild将使构建失败.而且我需要从头开始重新运行整个构建.这是时间 消耗.是否有任何方法可以使用msbuild设置的所有环境变量从msbuild环境中调试失败的项目,或者从那时开始再次使生成排队?

F1 F1 F1


关于Nain

解决方案

Nain,

如果您正在使用TFS Build和默认的构建定义模板,则可以定义要对工作空间执行的操作:

清洁工作区:
-所有         -将删除构建机器上的所有内容
-输出-将删除所有二进制文件,并仅从源代码管理中下载更改的文件
-无      -将保留所有内容,包括以前构建的二进制文件,并从源代码管理中下载更改的文件

因此,在您的情况下,请将其设置为无. ,因为它们已经构建,所以只会跳过前175个项目.


Hi

 We have build configured using msbuild and it runs for 276 projects. Now if a project fails after two hours say project # 175 failed to compile, then now MSBuild will fail the build. And i need to run the whole build again from start. This is time comsuming. Is there any way to debug the failed project from msbuild environment using all environment variable set by msbuild or queue the build again from that point? 

F1 F1 F1


Regards Nain

解决方案

Nain,

If you are using the TFS Build and using a default build definition template you can define what you want to do with the workspace:

Clean Workspace:
- All           - will delete everything on the build machine
- Outputs   - will delete all the binaries and will download only changed files from Source Control
- None       - will leave everything including the binaries build from the previous build and will download changed files from the Source Control

So in your case set this to None. It will just skip the first 175 projects because they are already build.


这篇关于调试由MSBuild排队的构建的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆