需要使用自定义构建脚本配置 TFS 构建
我使用以下脚本在 TFS 2010 构建服务器中对构建进行排队。如果我在本地使用以下命令,则此 TFSBuil.proj 会成功运行: MSBUILD.exe TFSBuild.proj
并获取我的暂存文件夹。 我正在努力将其构建到构建服务器中。最后,构建成功(8 秒内!),但最终什么也没做。日志指示成功调用但看不到结果的所有目标。非常感谢任何帮助,我准备为此携手努力。谢谢。
I use the below script to queue build in TFS 2010 build server. This TFSBuil.proj runs successfully if I use locally with command: MSBUILD.exe TFSBuild.proj
and get my staging folder. I am trying hard to get this to build in build server. Lastly the build ran to success (in 8 secs !) but did nothing at the end. Logs indicate all targets called with success but dont see the result. Any help is very much appreciated and I am ready to work hand in hand for this. Thank you.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
只是猜测(直到希望可以检索日志文件)..您是否尝试过从命令行使用 tf workfold 来验证工作文件夹映射?我会“在本地”执行此操作,然后在构建机器上执行此操作。您可以在具有足够权限的工作站上执行此操作,但转到构建计算机可能会帮助您看到意外的差异 - 这种情况在我身上发生过不止一次:-)。
另外,也许
..\
的定义不适合现有映射,即它比映射的级别高一级。希望这会有所帮助,
乔诺
Just a guess (until hopefully the log file can be retrieved).. have you tried to verify the work folder mappings using
tf workfold
from the command line? I would do that "locally" and then on the build machine. You can do this from your workstation with sufficient permissions, but going to the build machine might help you see unexpected differences - this happened to me more than once :-).Also, perhaps the definition of
<SolutionRoot>..\</SolutionRoot>
isn't appropriate for the existing mapping, i.e. it's going one level higher than what's mapped.Hope this helps,
Jonno