Beside adding, or uncommenting, the package VSTSVersionControl and deleting, or commenting out, Subversion in the Arguments.xml file...
You only need to set the property TFS.ServerUrl. An example would be something like this:
<property name="TFS.ServerUrl" value="http://thenameofyourtfsserver:8080" />
This
package assumes that the TeamProject is already created, it will not
create a TeamProject for you. By default it is configured to use a
TeamProject of the same name as the CI Factory you are creating
(remember this is set in the property ProjectName at the top of the
Arguments.xml file). If you do not want to have a one to one
relationship of CI Factory projects to TeamProjects, or said a
different way you want CI Factory projects to share a TeamProject you
need to edit the property TFS.ServerPathPrefix to include the
TeamProject name to be shared.
The way CI Factory integrates CCNet and TFS by subscribing to the
source control change event in TFS. This requires that the user CCNet
is running under have admin rights on the TFS server. Personally I
think that is a ridiculous situation, and I can't change it, that is
just the way Microsoft made it. So make sure that the user you log
into the windows machine hosting the CI Factory server has admin rights
to the TFS host OS.
You really shouldn't have a need to change anything else config
wise, unless you are hosting multiple CI Factory servers on one OS. If
so you will need to edit the two properties TFS.Listener.Port and
TFS.BuildScripts.Listener.Port to free/available ports for each new CI
Factory server after the first.
|
Documentation 
