tfs2010 - Steps for changing process template for an existing project in TFS 2010 -


i have tfs server installation through time has gone through upgrades tfs 2005 tfs 2008 , tfs 2010. during lifetime of installation lot of projects have been created , different project templates have been used. msf agile 4.0, 4.1, 4.2 , 5.0. , few msf cmmi ones.

what "replace" project template used these projects use new 1 common one: microsoft visual studio scrum 1.0.

i aware tfs project templates used templates creating new projects , cannot modify tfs projects definitions after creation.

uptil version control , build server part of tfs have been used , there no existing work item types.

additionally projects , build scripts depending on source code paths stay same.

as see have following options:

create new tfs projects using correct project template , move/branch source code new project.

  1. all code moved temporary team project.
  2. the old project deleted
  3. new project original name , correct process template created
  4. code moved new team project
  5. temporary team project deleted

    • all build definitions needs to recreated not option.

    • the source code move/branch "mess up" versioning history

alt text
messing versioning history mean when move source code behind scenes delete + source rename on original location , history still located in old project. make searching in history difficult , if delete old project loose history before source code move.

this not option me since there years of code change history needed supporting different applications being built.

use tfs migration tools migrate tfs project

  • this has same downsides first solution

replace/import work item types, install new reports, create new sharepoint sites

for each tfs project

  • delete existing work item definitions using "witadmin deletewitd"

  • import each work item definition new process template using "witadmin importwitd"

  • import work item categories using "witadmin importcategories"

  • delete old reports in project folder in report server

  • upload report definitions new process template

  • modify data sources used reports using report manager point correct shared data sources (tfsreportds , tfsolapreportsds)

  • modify report parameter explicitproject default value "" (empty string) , disable prompt user option.

  • export documents in old sharepoint site using stsadm

  • delete old sharepoint site

  • recreate sharepoint site using tfs2010 agile dashboard site template

  • activate site feature "team foundation server scrum dashboard"

  • in tfs project settings -> project portal settings: enable "team project portal" , ensure url correct. enable "reports , dashboards refer data team project"

and finally..

  • process warehouse

  • process analysis database

even though involves lot of small steps looks more appealing because option not force me move source code , existing build definitions intact.

my question:

are there other ways achieve replacement of work item types haven't mentioned?

and/or missing steps in last solution?

given aren't using existing work item types, final proposal looks best option.

after deleting old reports , exporting sharepoint documents (you use windows explorer instead of stsadm), there 2 commands in 'tfpt' you. reduce 14 steps down 5 or 6 steps.

tfpt addprojectreports  add or overwrite reports existing team project tfpt addprojectportal   add or move portal 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  

Comments

Popular posts from this blog

unicode - Are email addresses allowed to contain non-alphanumeric characters? -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

c++ - Convert big endian to little endian when reading from a binary file -