4

We are migrating a TFS 2012 project to TFS 2013 (project only has work items and no source code) and have a few questions about the agile project template.

  • In TFS 2012 if we want to create an Agile project then we have to choose: MSF for Agile Software Development 6.2
  • In TFS 2013 if we want to create an Agile project then we have to choose: MSF for Agile Software Development 2013.3

I want to know the following:

  1. Why is it that the TFS 2012 project with above template has a folder under it called 'BuildProcessTemplates', whereas the TFS 2013 project has no such folder?

  2. What is significance of the 'BuildProcessTemplates' folder, does the workitems data get stored in it? Can we get rid of it without affecting the workitem data?

  3. We are migrating a TFS 2012 project into TFS 2013 so we are wondering if we can delete the 'BuildProcessTemplates' folder after migrating to TFS 2013 without affecting the WorkItems.

James Skemp
  • 8,018
  • 9
  • 64
  • 107
Salim Mandrekar
  • 153
  • 7
  • Note: The "MSF for Agile" process templates are an agile implementation of the Microsoft Solution Framework, and not an 'agile' template. See:http://nakedalm.com/agile-vs-scrum-process-templates-team-foundation-server/ – MrHinsh - Martin Hinshelwood Jan 16 '15 at 19:20

1 Answers1

6

It's confusing terminology.

"Process Templates" and "Build Process Templates" are totally different things with no overlap.

A Process Template controls what work items you have available, how they interact, and the reports you get.

A Build Process Template controls how the TFS build system works. They are orthogonal to work items. You could delete the BuildProcessTemplates folder and it would have no impact on your work items, but I don't recommend doing so -- the folder contain the workflows that TFS can use to build your software for continuous integration or continuous delivery.

As of TFS2013, the folder isn't created because the built-in templates are stored internally. You only need to create a folder for the build process templates if you want to use custom templates, or modify the existing templates.

Daniel Mann
  • 57,011
  • 13
  • 100
  • 120
  • Hi Daniel, what are your comments on the point 3 mentioned by the OP? After migrating this agile team project from TFS 2012(which has got the buildprocesstemplates folder) to TFS 2013 (which has not got the buildprocesstempaltes folder), this folder from 2012 will sit in the TFS 2013 team project. Would it be safe then to delete it in TFS 2013? Safe means: Work items and structure, etc should be preserved :) – variable Jan 16 '15 at 07:14
  • @variable I can't be clearer: Build Process Templates have **nothing** to do with work items. – Daniel Mann Jan 16 '15 at 13:14