0

My Experiences Upgrading to TFS 2013 During “Upgrade Weekend”

by Angela 14. September 2013 13:56

So this weekend is officially TFS 2013 Upgrade Weekend.  What is that you ask? TFS evangelist extraordinaire Brian Keller blogged about it here, but in short it is a weekend where Microsoft is encouraging people to get on the TFS 2013 RC bits right away, and to incentivize us, product team people are on-line today to help us should we run into any issues. Sweet huh? :)

The TFS upgrade to 2013 was super fast and straightforward, I was literally done in under an hour including upgrading my build service. Unfortunately for me, I got up super early (had to get fresh flowers and donuts at the Oak Park farmers market!!) and kicked off my upgrade around 9:30am.  So by the time the upgrade support Lync meeting came on-line at 11:00am I was done with the install and had already started smoke testing. Not a bad problem to have right?

Well, at least I thought I was done. I did run into a few minor issues along the way, a few of my own doing and one bump related to my wireless being grumpy (OF ALL DAYS TO DO THAT!). But the only issue that was possibly related to the upgrade was corruption of my VS 2012 install bits.  When I smoke tested the upgrade, everything looked good until I started kicking off builds.  Some of my builds were no longer working ::sad trombone::  First, I had an issue with builds that ran automated UI tests:

Untitled3

I’d certainly seen this issue before, and it was always because the VS bits necessary to run the build were not installed on the build server.  But in my case I KNEW they were there, I had put them there myself some time ago! So I went to the server and out of curiosity I launched VS, and good thing I did.

image

::sad trombone #2::

I figured there must have been some kind of corruption after installing TFS 2013, or perhaps from upgrading the build service (they are on the same box), so I reinstalled VS 2012. No biggie…certainly fixed THAT issue.  However when I ran the build again, I encountered another error, this time around the data tools:

image

This error was even nice enough to link me directly to the place where I could download what I needed for a fix (i.e. reinstalling SSDT tools). So, after re-installing the data tools, I rebooted the server for good measure and the builds ran perfectly, everything looked good.  Lastly I installed VS 2013 RC as well, we will certainly need it as our folks will soon be chomping at the bit to use all of the new tools.  All I need to do now is configure a few projects to take advantage of the new Agile Portfolio Management features

So not a bad morning for a TFS upgrade, and if you haven’t upgraded yours, now you know how fast and easy it is :)  If you;re still nervous about going it alone, you don’t have to! Microsoft offers a program called Deployment Planning Services that many customers qualify for.  You may be eligible for free services (free consulting funding) from people like me that can help you get up and running on TFS, regardless of what version you want to upgrade to or what you are on today!

 

Lastly, MAD, MAD props to Microsoft and the TFS product team for offering free support today. Even though it was so smooth that I barely needed them. They seriously deserve a special sparkle pony award for their hard work, and for giving up a weekend to make sure we had everything we needed to succeed!

Tags:

Application Lifecycle Management | ALM | Build Automation | DTDPS | MSDN | SDLC | Team Foundation Server | TFS 2012 | TFS Upgrade | Visual Studio | Visual Studio 2012 | VS 2013 | VS 2012 | TFS 2013

Powered by BlogEngine.NET 2.7.0.0
Original Design by Laptop Geek, Adapted by onesoft