Builds from TFS 2010 do not contain in global list Builds node after upgrade TFS 2010 to TFS 2012 - by CSSForumEngineer

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 772465 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/28/2012 12:11:18 AM
Access Restriction Public


1. Queue build in TFS 2010 if there is not build in TFS 2010.
2. Open global list through process editor.
3. Builds already queued in TFS 2010 show in global list Builds node.
4. Upgrade TFS 2010 to TFS 2012. 
5. Open global list through process editor.
The result is builds from TFS 2010 do not show in the global list Builds node. Only builds queued in TFS 2012 show in the list.
Sign in to post a comment.
Posted by Microsoft on 1/28/2013 at 4:40 PM
This issue has been classified as "by design" by the product team. This behavior is due to a change in TFS 2012 that changed the format of the build names, which made it incompatible with those in 2010.

Currently, we cannot offer an official workaround, however there are some community projects to mitigate the issue. See below for an example:

Also see the following discussion thread for more information:

-Hakan Eskici
Team Foundation Server

Posted by Microsoft on 12/14/2012 at 1:30 PM
Hi CSSForumEngineer,

I am trying to repro this bug. However, I am not sure what "Open global list through process editor" means. Could you please step me through exactly what you are clicking on and in what application you are doing this.

Posted by Microsoft on 11/28/2012 at 11:40 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by BobHardister on 11/28/2012 at 5:21 AM
This is a serious problem for our users and is causing delay's in our collection upgrades. I reporting this on the forums here:
Posted by Microsoft on 11/28/2012 at 12:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(