Another one

In an effort to keep the remaining friends I have on LJ, I’ve decided to start posting my work experiences in a separate blog. We recently had a pretty nasty shake-up (or lay-offs, or “trimming the fat”, or “right-sizing”) at my company (lost about 60% of IT) and as a result, I found myself unexpectedly thrust into the Configuration Manager/Build Guy role. This was on top of my existing DBA responsibilities.

We’re a very small shop with only 5 developers now so some of our processes no longer made sense. Branching for every release to production, branching for every minor new project, queueing up tickets in our integration branch until the existing release was done so we could dump them onto our QA team all at once and give them 2 weeks to test it and get it out the door… none of this made sense anymore. This is especially true now that we’ve just gone from 1 QA lead to manage everything, 5 QA testers, and 2 dedicated CMs to just 1 QA manager/tester and me as CM/DBA.

All of this went down about a month ago. Since then, I’ve been slammed getting our CM stuff under control. We’re unquestionably a Microsoft shop and we use VS2005/TFS2005. Unfortunately our idea of CM has been looking over a list of changesets we think might need to be released, figuring out which assemblies and/or websites to deploy based on that list (we’re very n-Tier, so 1 assembly change might need to be deployed to 10 different apps), and then copying and pasting files around.

To try and get our heads out from under water, we’ve decided to upgrade to VS2008 and TFS2008. I’m not sure what VS2008 brings to the table for the developers beyond LINQ, but they seem pretty excited about just that aspect of it. TFS2008 though… that’s where the money is for me. 99% of the improvements I’ve run across in TFS2008 are on the build side and they kick ass, so we’ve crammed through an upgrade in the span of about 2 weeks that went live yesterday morning. The developers didn’t notice a thing… flawless.

Leave a Reply

Your email address will not be published. Required fields are marked *