在 TFS 2010 中更改现有项目的流程模板的步骤 [英] Steps for changing process template for an existing project in TFS 2010
问题描述
我有一个 TFS 服务器安装，随着时间的推移，它已经从 TFS 2005 升级到 TFS 2008，然后升级到 TFS 2010.在安装的生命周期内，创建了许多项目并使用了不同的项目模板.MSF 敏捷 4.0、4.1、4.2 和 5.0.和一些 MSF CMMI 的.
I have an TFS server installation that through time has gone through upgrades from TFS 2005 to TFS 2008 and then to TFS 2010. During the lifetime of the installation a lot of projects have been created and different project templates have been used. MSF Agile 4.0, 4.1, 4.2 and 5.0. and a few MSF CMMI ones.
我想做的是替换"用于所有这些项目的项目模板，以使用一个新的通用模板:Microsoft Visual Studio Scrum 1.0.
What I would like to do is "replace" the project template used for all these projects to use a new one common one: Microsoft Visual Studio Scrum 1.0.
我知道 TFS 项目模板用作创建新项目的模板，创建后无法修改 tfs 项目定义.
I am aware that TFS project templates are used as templates for creating new projects and cannot modify the tfs projects definitions after creation.
到目前为止，只使用了 TFS 的版本控制和构建服务器部分，并且没有现有的工作项类型.
Uptil now only the version control and build server part of TFS have been used and there are no existing work item types.
此外，所有项目和构建脚本都依赖于源代码路径保持不变.
Additionally all projects and build scripts are depending on the source code paths stay the same.
据我所知，我有以下选择:
As I see it I have the following options:
使用正确的项目模板创建新的 TFS 项目，然后将源代码移动/分支到新项目.
- 所有代码都移至临时团队项目.
- 旧项目被删除
- 创建了具有原始名称和正确流程模板的新项目
- 代码已移至新的团队项目
临时团队项目已删除
- All code is moved to a temporary team project.
- The old project is deleted
- New project with the original name and correct process template is created
- Code is moved to the new team project
Temporary team project is deleted
所有构建定义都需要重新创建，这不是一个选项.
All the build definitions needs to be to recreated which is not an option.
源代码移动/分支会弄乱"版本历史
The source code move/branch will "mess up" the versioning history
搞乱版本历史我的意思是当你移动源代码时，它会在幕后对原始位置进行删除 + 源重命名，而历史仍将位于旧项目中.这将使历史搜索变得困难，如果我真的删除旧项目，我将在源代码移动之前丢失所有历史记录.
By messing up the versioning history I mean that when you move source code it will behind the scenes do a delete + source rename on the original location and the history will still be located in the old project. This will make searching in the history difficult and if I actually delete the old project I will loose all the history before the source code move.
这对我来说真的不是一个选择，因为支持正在构建的不同应用程序需要多年的代码更改历史.
This is really not an option for me since there is years of code change history that is needed to for supporting the different applications being built.
使用 TFS 迁移工具迁移到另一个 TFS 项目
- 这与第一个解决方案有相同的缺点
替换/导入工作项类型、安装新报告、创建新 SharePoint 网站
对于每个 tfs 项目
For each tfs project
使用witadmin deletewitd"删除现有的工作项定义
Delete existing work item definitions using "witadmin deletewitd"
使用witadmin importwitd"从新流程模板导入每个工作项定义
Import each work item definition from the new process template using "witadmin importwitd"
使用witadmin importcategories"导入工作项类别
Import work item categories using "witadmin importcategories"
删除报表服务器项目文件夹中的旧报表
Delete old reports in project folder in report server
从新流程模板上传报告定义
Upload the report definitions from the new process template
使用报表管理器修改用于报表的数据源以指向正确的共享数据源(TfsReportDS 和 TfsOlapReportsDS)
Modify data sources used for the reports using the report manager to point to the correct shared data sources (TfsReportDS and TfsOlapReportsDS)
将报表参数 ExplicitProject 默认值修改为 ""(空字符串)并禁用提示用户选项.
Modify the report parameter ExplicitProject default value to "" (empty string) and disable prompt user option.
使用 stsadm 导出旧 SharePoint 站点中的文档
Export the documents in the old SharePoint site using stsadm
删除旧的 SharePoint 网站
Delete the old SharePoint site
使用 TFS2010 Agile Dashboard 站点模板重新创建 sharepoint 站点
Recreate the sharepoint site using the TFS2010 Agile Dashboard site template
激活站点功能Team Foundation Server Scrum 仪表板"
Activate site feature "Team Foundation Server Scrum dashboard"
在 TFS 项目设置 -> 项目门户设置中:启用团队项目门户"并确保 url 正确.启用报告和仪表板参考此团队项目的数据"
In TFS Project Settings -> Project Portal Settings: Enable "team project portal" and ensure the url is correct. Enable "reports and dashboards refer to data for this team project"
最后..
处理仓库
Process the Warehouse
处理分析数据库
尽管这涉及很多小步骤，但这看起来更有吸引力，因为这个选项不会强迫我移动源代码，我现有的构建定义将保持不变.
Even though that this involves a lot of small steps this looks more appealing because this option will not force me to move the source code and my existing build definitions will be intact.
我的问题:
是否有其他方法可以实现我没有提到的工作项类型的替换?
Are there other ways to achieve the replacement of work item types that I haven't mentioned?
和/或我是否遗漏了上一个解决方案中的任何步骤?
And/or am I missing any steps in last solution?
推荐答案
鉴于您没有使用任何现有的工作项类型，您的最终提案看起来是最佳选择.
Given that you aren't using any existing work item types, your final proposal looks like the best option.
删除旧报表并导出 SharePoint 文档(您也可以使用 Windows 资源管理器而不是 stsadm)后，'tfpt' 这将对您有所帮助.这会将其从 14 步减少到 5 或 6 步.
After deleting the old reports and exporting the SharePoint documents (you could also use Windows Explorer instead of stsadm), there are actually two commands in 'tfpt' that will help you. This will reduce it from 14 steps down to 5 or 6 steps.
tfpt addprojectreports Add or overwrite reports for an existing team project
tfpt addprojectportal Add or move portal for an existing team project
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
tfpt addprojectreports /collection:http://yourtfs:8080/tfs/YourCollection /teamproject:"Your Team Project" /processtemplate:"Microsoft Visual Studio Scrum 1.0" /verbose
这篇关于在 TFS 2010 中更改现有项目的流程模板的步骤的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
