Applying Patches
Microsoft Visual Source Safe Integration
To apply patch for vss-native.exe:
Shut down TeamCity server
Open
<TeamCity Home>/webapps/root/WEB-INF/plugins/vss/or<TeamCity Home>/webapps/root/WEB-INF/lib/folderBack up
vss-support.jarfileInside
vss-support.jarfile, replace/bin/vss-native.exewith the new oneStart the server
To apply full VSS plugin patch:
Shut down TeamCity server
Open
<TeamCity Home>/webapps/root/WEB-INF/plugins/vss/or<TeamCity Home>/webapps/root/WEB-INF/lib/Back up
vss-support.jarReplace
vss-support.jarwith the new oneStart the server
Capturing Logs From VSS-native
Each time TeamCity starts, it creates a new instance of the vss-native.exe file and places it to the <TeamCity home>/temp folder. The name of the copy is generated automatically and uses the following template: TC-VSS-NATIVE-<some digits>.exe
To manually enable detailed logging (for debugging purposes) for VSS Native:
Copy the
<TeamCity Home>/temp/TC-VSS-NATIVE-<some digits>.exefile to any folder.Run the program with
/logswitch. To get the commandline syntax and options reference, run the program without any switch.
Microsoft Team Foundation Server Integration
To apply the patch for tfs-native.exe:
Shutdown TeamCity server
Open
<TeamCity Server>/webapps/root/WEB-INF/plugins/tfs/or<TeamCity Server>/webapps/root/WEB-INF/lib/Backup
tfs-support.jarInside the
tfs-support.jarfile, replace/bin/tfs-native.exewith the new oneStart the server
To apply full TFS plugin patch:
Shutdown TeamCity server
Open
<TeamCity Home>/webapps/root/WEB-INF/plugins/tfs/or<TeamCity Home>/webapps/root/WEB-INF/lib/Back up
tfs-support.jarReplace
tfs-support.jarwith the new oneStart the server
Capturing logs from TFS-native
To enable creating logs from TFS-native:
Locate
tfs-native.exeunder TeamCitytempfolder. File name should look likeTC-TFS-NATIVE- <digits> .exeCreate a copy of the file in any other folder.
Run this program with
/logswitch.
To get command-line switches help, run the process with no parameters. Log files will be created <TeamCity agent>/temp/buildTmp/TeamCity.NET folder. For each process a new log file will be created.
.NET runners
To patch .NET part of .NET runners:
Open
<TeamCity Server>/webapps/root/update/plugins/Copy
dotNetPlugin.zipto temporary folderBack up
dotNetPlugin.zipExtract
dotNetPlugin.zipReplace contents of
/binfolder with new files.Pack files again. Make sure there are no files in the root of the archive.
Replace
dotNetPlugin.zipfile on the server. All build agents will upgrade automatically.Run the builds.
To enable logging from .NET runners:
Open
<TeamCity Server>/webapps/root/update/plugins/Copy dotNetPlugin.zip to temporary folder
Back up
dotNetPlugin.zipExtract
dotNetPlugin.zipCopy
/bin/teamcity-log4net-debug.xmlto/bin/teamcity-log4net.xmlYou may patch Log4NET config file if you need.
Pack files again. Make sure there is no files in the root of the plugin archive.
Replace the
dotNetPlugin.zipfile on the server.All build agents should upgrade automatically.
Run the builds.
By default, all of the log files will be stored in the <TeamCity agent>/temp/buildTmp/TeamCity.NET folder, log files are created for each process separately.