体验TFS Build,要想实现每日Build,这个是不错的工具,
之前TFS B3R安装TFS Build老是不成功,作为配置管理员可是很着急啊.
现在TFS Workgroup Edtion安装之后终于可以看看Build的庐山面目了.
先新建一个Build Type,有向导
选择哪个解决方案:
![](/images/cnblogs_com/cleo/NewBuildType_selections.png)
选择Build服务器及Build之后文件放置的路径:(我新建EMABuild目录,并且共享)
![](/images/cnblogs_com/cleo/NewBuildType-Location.png)
这里可以选择运行Test和Code Analysis
![](/images/cnblogs_com/cleo/NewBuildType-options.png)
完成之后运行Build:出错了!
![](/images/cnblogs_com/cleo/build-error.png)
一看日志:
事件类型: 错误
事件来源: TFS Build
事件种类: 无
事件 ID: 3000
日期: 2006-3-26
事件: 23:25:47
用户: N/A
计算机: TFSWE
描述:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 2006-3-26 15:25:47
Machine: TFSWE
Application Domain: TFSBuildService.exe
Assembly: Microsoft.TeamFoundation.Build.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: TFSBuildService
Process Id: 392
Thread Id: 3928
Account name: TIANCHI\tfsservice
![](/Images/OutliningIndicators/None.gif)
Detailed Message: 对路径“\\TFSWE\EMAbuild\EMAConfictCheckBuild_20060326.1”的访问被拒绝。
Exception Message: 对路径“\\TFSWE\EMAbuild\EMAConfictCheckBuild_20060326.1”的访问被拒绝。 (type UnauthorizedAccessException)
![](/Images/OutliningIndicators/None.gif)
Exception Stack Trace: 在 System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
在 System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity)
在 System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity)
在 Microsoft.TeamFoundation.Build.Common.IOUtils.CreateDirectoryIfNotExist(String dirPath)
在 Microsoft.TeamFoundation.Build.Client.BuildAgent.EnsureDropLocationExists(BuildStore buildStore)
在 Microsoft.TeamFoundation.Build.Client.BuildAgent.ProcessExited(Object Sender, EventArgs e)
![](/Images/OutliningIndicators/None.gif)
原来是我在共享EMABuild目录的时候只做了Everyone只读共享,但是TFS Build原来是要通过这个共享写文件的,所以出错了,我修改权限之后,Build成功,激动:
![](/images/cnblogs_com/cleo/build-ok.png)
你可以清楚地看到,每个Build都是可以和changeset和workitem相关联的:
![](/images/cnblogs_com/cleo/build-changeset.png)
这下,你可以要求你的组员在迁入的时候记得写上Comments了,因为这些Comments又多了一个用处(除了在源代码查找的时候).
你可以看看某个Build Type的Build纪录和修改Build的Quanity
![](/images/cnblogs_com/cleo/build-quanity.png)
不过还要修改Build Type就没有可视化的向导界面的,修改代码吧,不过代码里肯定有更多的定制选项留给我们的:
![](/images/cnblogs_com/cleo/build-code.png)
结论: 要想实现每日Build,这个是不错的工具,而且可以关联Changeset和Workitem,便于Tester跟踪.
体验TFS Build就先到这里,下次看看代码里有哪些定制功能.
现在TFS Workgroup Edtion安装之后终于可以看看Build的庐山面目了.
先新建一个Build Type,有向导
选择哪个解决方案:
![](/images/cnblogs_com/cleo/NewBuildType_selections.png)
选择Build服务器及Build之后文件放置的路径:(我新建EMABuild目录,并且共享)
![](/images/cnblogs_com/cleo/NewBuildType-Location.png)
这里可以选择运行Test和Code Analysis
![](/images/cnblogs_com/cleo/NewBuildType-options.png)
完成之后运行Build:出错了!
![](/images/cnblogs_com/cleo/build-error.png)
一看日志:
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
![](/Images/OutliningIndicators/None.gif)
原来是我在共享EMABuild目录的时候只做了Everyone只读共享,但是TFS Build原来是要通过这个共享写文件的,所以出错了,我修改权限之后,Build成功,激动:
![](/images/cnblogs_com/cleo/build-ok.png)
你可以清楚地看到,每个Build都是可以和changeset和workitem相关联的:
![](/images/cnblogs_com/cleo/build-changeset.png)
这下,你可以要求你的组员在迁入的时候记得写上Comments了,因为这些Comments又多了一个用处(除了在源代码查找的时候).
你可以看看某个Build Type的Build纪录和修改Build的Quanity
![](/images/cnblogs_com/cleo/build-quanity.png)
不过还要修改Build Type就没有可视化的向导界面的,修改代码吧,不过代码里肯定有更多的定制选项留给我们的:
![](/images/cnblogs_com/cleo/build-code.png)
结论: 要想实现每日Build,这个是不错的工具,而且可以关联Changeset和Workitem,便于Tester跟踪.
体验TFS Build就先到这里,下次看看代码里有哪些定制功能.
posted on 2006-03-27 00:14 无为而为-凡事从积极的态度做起 阅读(2370) 评论(0) 编辑 收藏 举报