Reputation: 41
We started using TFS 2010 earlier this year as a code repository for a new project. To date we have not added work items to the project but plan to do so very soon (currently using TestTrackPro). When the project was created, Agile was selected.
The client now wants the CMMI process template to be used instead. While it is understood that we will need to create a new project and select the CMMI process template, the main directive is to NOT lose code history. Is it as simple as creating a branch from the existing project and binding to the new project? What are the "gotcha's" to look out for, etc.
We have build defs that will not migrate over; no problem as there are not many and not hard to reproduce. We are in a closed network, so bringing over open-source applications is not so simple. And it seems like TFS Integration Platform and witadmin might be overkill. We don't have any TFS experts at our disposal so any thoughts/suggestions/approaches would be appreciated.
Upvotes: 4
Views: 998
Reputation: 4101
Based on my own experience ( government contracts ) freeze the original project and code base and then create the new committee project and migrate the code tree, that way the history is not lost and if any of the work item templates were modified, this mitigates the risk of merging the two process templates incorrectly
Upvotes: 0
Reputation: 9189
It's possible, but it requires heavy use of command line tools like witadmin
There's another thread which goes into this scenario quite deeply but there's a few steps which can be done easier.
Using the tfs administrators toolkit you can certainly simplify the updating of reports, if you happen to have another project with the correct work item templates you can also use it for that instead of witadmin.
(Below is copied from mentioned thread)
Work Items
Either use the tfs admin toolkit mentioned above or witadmin
Update Reports
Either use the tfs admin toolkit mentioned above or tfpt
tfpt addprojectreports Add or overwrite reports for an existing team project
SharePoint
tfpt addprojectportal Add or move portal for an existing team project
Upvotes: 1
Reputation: 22245
The branch and re-bind approach you suggested sounds like it would work fine in your case.
Upvotes: 0