Geeks With Blogs


Jakob Ehn Visual Studio ALM MVP - Works @ActiveSE April 2010 Entries
Modify Build Failure Work Item in TFS 2010 Build
The default behaviour in TFS Team Build (all versions) is to create a bug work item when a build fails. This main benefit of this is that you get a work item for something that needs to be done, namely to fix the build!. When the developer responsible for the build failure has fixed the problem, he/she can associated that check-in with the work item that was created from the previous build failure. In TFS 2005/2008 you could modify the information in the created work item by changing some predefined ......

Posted On Wednesday, April 28, 2010 8:15 AM

Creating a Build Definition using the TFS 2010 API
*** UPDATE 2010-08-17 ** Several people have asked me for a complete sample application, so I have put this together and it is available here: http://cid-ee034c9f620cd58d... **** In this post I will show how to create a new build definition in TFS 2010 using the TFS API. When creating a build definition manually, using Team Explorer, the necessary steps are lined out in the New Build Definition Wizard: So, lets see how the code looks ......

Posted On Monday, April 26, 2010 8:09 PM

Getting TF215097 error after modifying a build process template in TFS Team Build 2010
When embracing Team Build 2010, you typically want to define several different build process templates for different scenarios. Common examples here are CI builds, QA builds and release builds. For example, in a contiuous build you often have no interest in publishing to the symbol store, you might or might not want to associate changesets and work items etc. The build server is often heavily occupied as it is, so you don’t want to have it doing more that necessary. Try to define a set of build process ......

Posted On Wednesday, April 21, 2010 11:52 PM

Implementing Release Notes in TFS Team Build 2010
In TFS Team Build (all versions), each build is associated with changesets and work items. To determine which changesets that should be associated with the current build, Team Build finds the label of the “Last Good Build” an then aggregates all changesets up unitl the label for the current build. Basically this means that if your build is failing, every changeset that is checked in will be accumulated in this list until the build is successful. All well, but there uis a dimension missing here, regarding ......

Posted On Thursday, April 15, 2010 11:50 PM

Copyright © Jakob Ehn | Powered by: | Join free