Martin Hinshelwood recently posted about the current state of TFS sync and migration tools here and while I thought the post was very detailed and covered the market pretty well I think he did miss one smaller tool that I’ve used with some success: TFS Bug Item Synchronizer .
Now I don’t know what his criteria was for the article and if perhaps this tool didn’t fall into some category but I definitely think it is worth a look especially for smaller companies with smaller budgets or even TFS teams that might not need one of the huge enterprise solutions. (and it even has a trial period)
From the product site
TFS Bug Item Synchronizer is an tool which allows testing and development teams to work together using tools built for their usage. Testers enter defects in Quality Center and when defect is created and updated into TFS, developer can fix it, link all changes to it and mark it as fixed. After this the tester will continue process on Quality Center side to verify the fix.
I implemented this product last year and like most sync tools it takes a little up front work and definitely some understanding of how TFS works but the support that was available was incredibly helpful and you can’t beat the price point.
So hopefully this will add one more tool to what seems to be an ever growing list of tools in this space. Now if we can just get one that requires little to no configuration 😉
In Team Foundation Server when running the Builds report you are presented with a list of Build instances that have run in the past and a few columns of useful data such as Quality, Tests Passed, % Code Coverage. The build names themselves are intended to be clickable to show you the build details screen for that build but often times when clicking one of these links you will see the following message:
InvalidBuildUriExceptionTF215070: The build URI 5087 is not valid. Make sure that this build exists and has not been deleted.
This error is simply telling you that the Build result for this particular build no longer exists. This is most likely due to your retention settings for the build. I defaulted my builds to only keep the 2 latest builds thinking that would be a good way to save space, blah blah but in the end it means that all information about that build is removed INCLUDING the build details and label on your code! I found more information on build retention and how to correct this in a blog post HERE
Now if I could only find out how to cleanup that Build Dropdown list on this report….
I’m at the end of a 2 day TFS 2008 install marathon (yes, the one with the “fixed” installer) and I needed to move my WSS 3.0 config database (wss_config) to a new database which requires essentially creating a new wss_config database with the proper settings and I found an article about using PSConfig.exe to create/configure everything magically for you. Now remember this is a Microsoft tool, recommended in MSDN and installed by WSS 3.0 so of course I trust that it does what it says. Well, let me just say this
NEVER, EVER, EVER, EVER use this tool!
I ran it with the configdb command -create and oh yes I got my shiny new database but in the process it deleted my ENTIRE wwwroot folder. I have no idea how or why but something is REALLY wrong deep down in this code. If you wrote this code PLEASE feel free to contact me to discuss and I will gladly retract my statements but in the meantime save yourself the trouble. I think STSAdm.exe might still do the job or perhaps you can do it from the Admin screens (not sure) but avoid this tool