An early look at Team Foundation Build 2010 with Jim Lamb
- Posted: Oct 03, 2008 at 9:47 AM
- 58,828 Views
- 10 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- WMV (WMV Video)
In addition to being one of the nicest guys I know, Jim Lamb also knows a thing or two about build automation. Jim is the program manager responsible for the Team Build capability of Team Foundation Server.
Team Build was one of the biggest areas of improvement for Team Foundation Server 2008, but that hasn't stopped the team from doing even more landmark improvments in Team Foundation Server 2010.
Jim shows off how Team Build 2010 will take advantage of Windows Workflow, build agent pooling, distributed asynchronized builds, and two new types of build called "buddy builds" and gated check-ins.
This "Humanized Screencast" is best viewed at fullscreen using the high-quality WMV download.
Jim shows off how Team Build 2010 will take advantage of Windows Workflow, build agent pooling, distributed asynchronized builds, and two new types of build called "buddy builds" and gated check-ins.
This "Humanized Screencast" is best viewed at fullscreen using the high-quality WMV download.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Team Build is build on top of MSBuild. So if your language already has an MSBuild task (several do) you should use that. Else you can use the generic MSBuild "exec" task to call any .EXE, .BAT, etc.
My posts are expressing an interest in being able to instantiate build as a .Net object. For that matter, I'd like to instantiate MS compilers, VS, IL assember, IL disassember and PEVerify. No more Exec-ing, batching, or cryptic COM stuff. That's the way I write compilers and tools and wish others did it the same way.
Create a Basic Language Service Using the Managed Babel System
Say I'm working on a project that has a certain build process in place and it gets shipped, the code will be branched and I'll carry on working on the main trunk. If I needed to fix a bug in the earlier branch of the code, I would want to be confident that any build I perform against it was the exact build process that was around when the branch occurred. (You could kind of do this in team build 2008 by storing the build script within the workspace of the solution)
The build processes I've been involved in do more than just build the solution, they also package and in some cases deploy the application binaries, as well as upgrading databases. It would seem to me that these "processes" fit better with the new build workflow you demonstrated, but if they are "global" build definitions and not tied to a specific branch of the app, then I'd still have to use my current msbuild approach.
Is there any way in team build 2010 to "branch" these build processes? If not, how would you recommend branch builds be maintained?
A product enhancement request related to Project Alerts area w.r.t. Team Builds. As of now, TFS provides 2 team project level related to team builds i.e.,
1. When a build completes
2. When a build quality changes
But in practical world, the audience/stakeholders for these alerts is always different for each build type lets say a scenario for Daily Build vs Bi-weekly build or Development Build vs Release Build. Same holds true for the build quality changes of these builds. A QA / UAT / PRODUCTION resource is not interested in all the builds and its quality changes except the Release Build.
Request : So, It would be nice to have Build Alerts a part of build type definition itself. The project alerts at the team project level will still be beneficial at the project team level / project managers and above ....
Hi, James,
I see in your screen that you have many features under the Process tab in the build definition. Currently I have installed VS2010 and when I try to create a new definition I see just a few features to con figure, and the look like of the build definition windows is quite different. Do I have to install some add-in?
Remove this comment
Remove this thread
close