Channel 9 interview and demo of Orcas Team Build

Giving Microsoft Dev Division their props

Bryan Hinton's Blog — Thu, 17 Apr 2008 00:46:02 GMT

I have been meaning to blog on this for a days now - today I decided to stop procrastinating. Most have

Orcas Beta 1 has shipped - summary of Team Build beta 1 features and links

Buck Hodges — Mon, 23 Apr 2007 18:04:21 GMT

As you probably already know, Orcas Beta 1 has shipped. Internally, the product team is focused on finding

Stop piling on when the build breaks: Build checkin policy for Continuous Integration in Orcas

Buck Hodges — Thu, 29 Mar 2007 02:13:47 GMT

Last fall, Clark Sell wrote a blog post called Stop, the build is broken!! that introduced a checkin

Aaron's back and has new posts on Team Build

Buck Hodges — Wed, 21 Mar 2007 21:01:59 GMT

Aaron Hallberg took a month off after the birth of his daughter, Stella . Now that he's back, he's got

re: Channel 9 interview and demo of Orcas Team Build

Aaron Hallberg — Mon, 19 Mar 2007 17:02:09 GMT

This will be quite simple in Orcas, Mike - you'll be able to set the output subdirectory for each item in the SolutionToBuild item group individually through Properties metadata. Something like this:

<Properties>OutDir="$(BinariesRoot)\foo"</Properties>

</SolutionToBuild>

We're also exposing a property, called $(TeamBuildOutDir), that you can use to customize output subdirectories for each project within a solution - typically you would do this by setting the OutputPath within your project to something like:

$(TeamProjectOutDir)foo

Outside of a Team Build build, $(TeamProjectOutDir) will evaluate to the empty string; within a Team Build build it will evaluate to the current default output location.

TFS shipped one year ago today!

Buck Hodges — Sat, 17 Mar 2007 18:19:36 GMT

As Jeff Beehler points out , we shipped TFS one year ago today. In the intervening time, we reorganized

re: Channel 9 interview and demo of Orcas Team Build

Mike Bouck — Sat, 17 Mar 2007 02:31:27 GMT

Sounds like great stuff is coming -- keep up the good work!

One thing that we're strugging with in v1 is that for a given Build Type, all selected solutions get their outputs dumped into the same drop directory. This is fairly useless as I have no way of knowing which build outputs belong to a specific solution in a deployment scenario. The way we're working around this currently is to define a seperate Build Type per solution -- hardly ideal. Any improvements in this area? Thanks!

VSTS Links - 03/15/2007

Team System News — Thu, 15 Mar 2007 17:05:15 GMT

J.D. Meier on Structuring Projects for Team Foundation Server. Buck Hodges on Channel 9 interview...