It seems odd that the main build definitions would not have a history, but I can't find any mechanisms. Please tell me there is someway to track changes to the build definitions over time.
views:
21answers:
2
A:
Look in source control under:
$/ProjectName/TeamBuildTypes
There should be a full history of changes to the <>.proj file stored there.
Robaticus
2010-06-07 17:13:26
those .proj files are from team build 2008, the same structure and files do not exist in TFS 2010. That is the whole problem, there is no file saved anywhere. It must just keep the build steps in the database.
Alex
2010-06-07 18:52:06
Thanks for that update. I figured because TFS 2010 made the TeamBuildTypes directory, that it would populate it with something.
Robaticus
2010-06-07 19:17:39
Alex-- I still haven't found anything on the inherent ability to track build changes over time, but one thing you could do is export the build and store that in source control. Kludgy, but might work.
Robaticus
2010-06-10 13:50:59
A:
You can use the .proj files in TFS 2010 builds (for backwards compatibility). So, if you really needed to track changes, just add the .proj file to the appropriate TeamBuildTypes folder. When you create the build definition, on the Process form, you need to change Build process file to 'Upgrade Template' and then specify the Configuration Folder Path under Build process parameters.
Rick D
2010-06-23 17:57:00