Attaching Custom Data to a Build

In Orcas, we introduced a generic information storage for builds – internally this is used for all build steps, associated changesets/workitems, etc.  You can use it to attach arbitrary data to a build (and later retrieve it).  Here are a couple of quick code snippets to illustrate these two cases. To attach a single name/value…

2

Orcas RTM Object Model Documentation

The official Orcas RTM OM documentation was posted a while ago, and I neglected to blog about it!  It’s available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=6466b53d-d80b-4c31-8f5c-dfb5d32e9411&DisplayLang=en.  Make sure to follow the instructions for viewing it after downloading: Method 1 Double-click the .chm file. In the Open File-Security Warning dialog box, clear the Always ask before opening this file check…

0

Tech*Ed 2008

If you are planning on attending Tech*Ed Developers in sunny Orlando this year, I’ll be manning the Visual Studio Team System 2008 Team Foundation Server (Version Control and Build) demo station (quite the name, eh?) for about 22 hours over the course of the four day event.  Please stop by and say hello, ask some…

1

Orcas SP1 TFS Build Changes, Part 2

As promised, here are some more details on other SP1 changes for TFS Build.  3. Detect test results. In Whidbey, a failed test would result in a failed build – builds were either Succeeded or Failed, so there wasn’t really much middle ground.  In Orcas we added two new build status properties, CompilationStatus and TestStatus;…

3

Orcas SP1 TFS Build Changes

Brian Harry put up a post on the improvements that will be available in the upcoming Team Foundation Server 2008 SP1 release.  Here’s some more in depth info on two of the TFS Build changes: 1. Conditionalize builds on the trigger. There are actually a few changes here…  Essentially we exposed a property on IBuildDetail…

10