TFS Dependency Replicator

COMMENTED ISSUE: Add a sample DependencyReplicator.xml file.

ihatescarves — Tue, 19 Feb 2008 00:21:47 GMT

A sample DependencyReplicator.xml file would help teams get started using this tool.
Comments: ** Comment from web user: ihatescarves **

Here's an example for a project that has two build types requiring dependency replication. The assemblies compiled in the first build type will be replicated every time the build is successful; the assembly in the second build type will only be replicated once the build is marked as "DevelopmentAccepted".(I haven't actually used that feature, but I think the syntax is correct).

COMMENTED ISSUE: Checking in dependencies after build as one ChangeSet

ihatescarves — Mon, 11 Feb 2008 06:14:10 GMT

At the moment after the build each dependency is checking in as a separate Changeset, so multiple changeset are created for a single build.

It will be logical if all dependencies for the project/solution will be checked in as one changeset.

Note that Mitch Danny warn that the complexity of recovering from a single DLL not being able to checked in wasn't worth it and think that current approach is more reliable.

May be it can be added as a configuration option.
Comments: ** Comment from web user: ihatescarves **

I think this is a choice idea - having 1 changeset for each dependency really stinks up the history.

Source code checked in

MitchDenny — Fri, 08 Feb 2008 08:31:11 GMT

Updated code - compiled against the TFS2008 assemblies. There are some obsolete warnings but I will see if there is enough compatibility to work in our internal environment, then we will resolve the issues for the 1.1 release.

Source code checked in

MitchDenny — Fri, 08 Feb 2008 08:28:36 GMT

This check-in is a branch of the 1.0 code to get it working under Team Foundation Server 2008. This branch will be tested at Readify after a simple re-compile, and if it proves to be OK it will be merged into the Trunk and we will do a 1.1 release with it.

CREATED ISSUE: Checking in dependencies after build as one ChangeSet

mfreidge — Thu, 07 Feb 2008 00:46:58 GMT

CREATED ISSUE: Add a sample DependencyReplicator.xml file.

MitchDenny — Thu, 24 Jan 2008 23:11:17 GMT

A sample DependencyReplicator.xml file would help teams get started using this tool.

UPDATED WIKI: Positions Vacant

MitchDenny — Fri, 14 Dec 2007 10:47:54 GMT

Positions Vacant

We are currently in need of the following specific skills on this project. If you are interested, please contact Mitch Denny.

Documentation Writer; responsible for updating CodePlex wiki and producing installation guide.
Tester; responsible for testing installation process and operation of the tool.
Developer; joint responsibility with me in designing and developing the TFS Dependency Replicator moving forward.

UPDATED WIKI: Positions Vacant

MitchDenny — Fri, 14 Dec 2007 10:47:01 GMT

Positions Vacant

We are currently in need of the following specific skills on this project. If you are interested, please contact Mitch Denny.

Documentation Writer; responsible for updating CodePlex wiki and producing installation guide.
Tester; responsible for testing installation process and operation of the tool.*
Developer; joint responsibility with me in designing and developing the TFS Dependency Replicator moving forward.

UPDATED WIKI: Home

MitchDenny — Fri, 14 Dec 2007 10:43:52 GMT

Welcome

Welcome to the TFS Dependency Replicator project homepgage, to see what this project is all about please refer to our project description.

Project Description

The TFS Dependency Replicator is a tool that monitors the Team Foundation Server Build Store for the successful completion of new builds, or the change in qualify status of existing builds. When a change is detected TFS Dependency Replicator looks up a configuration file in the version control store and determines if any files from the build drop location need to be copied back into the source tree.

TFS Dependency Replicator is useful for complex build scenarios where a common framework is used across a range of products and once a new build of that framework is completed it needs to be published back into the source tree in binary for so other code bases automatically start using it.

This tool saves development teams the tedious task of manually updating binary dependencies produced from upstream builds.

Positions Vacant

If you would like to help out with this project, please visit our Positions Vacant page.

CREATED RELEASE: TFS Dependency Replicator 1.0 (RTM) (Dec 14, 2007)

Fri, 14 Dec 2007 10:42:16 GMT

This is the first public release of TFS Dependency Replicator 1.0 and is ready for immediate use. This version of TFS Dependency Replicator has been used reliably in production by Readify for a number of months and supports Team Foundation Server 2005.

Source code checked in

MitchDenny — Fri, 14 Dec 2007 10:35:20 GMT

This is the RTM branch of TFS Dependency Replicator. We will release from here.

Source code checked in

MitchDenny — Fri, 14 Dec 2007 10:32:16 GMT

This is the initial check-in of the TFS Dependency Replicator. It is designed to work with Team Foundation Server 2005. We will create an RTM branch and release from that then start getting it stabilised for Team Foundation Server 2008.

Source code checked in

MitchDenny — Fri, 14 Dec 2007 09:32:08 GMT

This is the initial check-in setting up the structure of the source tree.