Hello!

As of Go 12.1, Go has native TFS SCM support.  Check this out.

--Mark Chang

----

Many Team Foundation Server (TFS) customers are hungry for more flexible, configurable and open build solutions. Go does not support direct integration with TFS. That will change, but until then there is a workable solution using SvnBridge.

NOTE: I tested this with TFS 2010, but the set up for TFS 2008 *should* be the same.

You can install SvnBridge either on each client PC or centrally as a web site on a server. The latter for conveniance and ease of maintenance over a team. In server-mode it goes on the TFS application tier machine. If you have TFS all on one box, then that's the application tier, too. Follow the installation instructions to install SvnBridge.

IMPORTANT: The account used by the IIS application pool assigned to the SvnBridge web application needs to be an authorzed user with access to the areas of TFS source control for the code being access via SvnBridge.

RECOMMENDED: Install SvnBridge on the TFS application tier so it does not have to be configured as a client on your GO Windows agents.

TFS 2010 supports the notion of Team Project collections. If you have more than one project  collection then you need a separate SvnBridge application on the TFS app tier for each collection. The information below shows you how to set up for multiple project collections. If you are using TFS 2008 or only use one project collection just configure a single collection.

SVNBRIDGE WITH TFS 2010 ON IIS 7.5

Configuring SvnBridge for multiple project collections is not difficult, but it pays to be organized.  

1. You need a separate web app for each collection. I bundled them in a hierarchy under a single web site to keep things tidy.
2. You need to configure web.config for each web app to point to a project collection as follows:

 <add key="TfsUrl" value="http://localhost:8080/tfs/DefaultCollection/" />

I defined a hierarchy that looks like this. Note that a separate copy of the SvnBridge app is needed for each collection directory. These cirectories become the target for each collection's web app.

• SvnBridge
  • DefaultCollection
    • bin
    • Logs
    • web.config
  • MyCollection
    • bin
    • Logs
    • web.config

I defined a site called SvnBridge and put it on port 8081 pointing at the SvnBridge directory. I also made sure that this site was assigned to an ASP.NET 4.0 application pool running in integrated mode. 

IMPORTANT: The account used by the IIS application pool assigned to the SvnBridge web application needs to have access to the areas of TFS source control for the code being access via SvnBridge. 

• I recommend creating a special account in Windows for this and giving it read access on all the Team Projects with source libraries you're using in GO pipelines.
• I recommend you use the same account to run the SvnBridge application pool AND the GO Agent process on Windows. 
• I recommend that this be a separate "service" account with a well-protected password for good SOX/PCI governance.

I defined applications under SvnBridge called DefaultCollection and MyCollection respectively and pointed their target directory at the like-named directory, which contains a copy of SvnBridge code.

I set the respective TfsUrl key values under <Appsettings> in each web.config appropriately.

CONFIGURING GO

The code snippet below is an example of a GO pipeline to build using SvnBridge. This pipeline runs a build of a Visual Studio solution using Rake. Details for doing this are here. 

To reference the project called test use http://mytfsserver:8081/DefaultCollection/test or http://mytfsserver:8081/MyCollection/test if not using the DefaultCollection. 

The username attribute of the svn tag denotes the fully-qualified Windows domain name of the user in TFS, in this case, me.