I just finished reading Buck Hodges’ posting about the Team Build features that are forthcoming in Orcas. It’s a laundry list of items that I’ve been struggling with in the CI space for months and months now.
“Brian Harry posted a TFS roadmap. I’d like to expand on the portion that describes the features specific to Team Build. Keep in mind that these features can change before Orcas ships, so there are no guarantees that it will match what’s described below.
- Support multi-threaded builds with the new MSBuild.
- Continuous Integration – There are many components to this, including build queuing and queue management, drop management (so that users can set policies for when builds should be automatically deleted), and build triggers that allows configuration of exactly how when CI builds should be triggered, for example – every checkin, rolling build (completion of one build starts the next), etc.
- Improved ability to specify what source, versions of source, and other build properties.
- Improved extensibility of the build targets – such as ability to easily execute targets before and after each solution/project is built.
- Improved ability to manage multiple build machines.
- Stop and delete builds from within VS.
- .NET Object model for programming against the build server.
- Simplified ability to specify what tests get run as part of a build.
- The ability to story build definitions anywhere in the version control hierarchy.”
The most encouraging statement in his post was:
“Continuous Integration is the flagship feature for Team Build in Orcas.”
So I’ll start keeping abreast of the work being done in Orcas and make sure that my CI and Enterprise builds are compatible, or at least can be easily migrated to the new version.
Thanks for the update Buck and please keep us informed of the cool new stuff you guys are getting ready for us!