Applying Patches
Microsoft Visual Source Safe Integration
To apply the patch for vss-native.exe
:
Shutdown TeamCity server
Open
<TeamCity Home>/webapps/root/WEB-INF/plugins/vss/
or<TeamCity Home>/webapps/root/WEB-INF/lib/
folderBack up
vss-support.jar
fileInside
vss-support.jar
file, replace/bin/vss-native.exe
with new oneStart the server
To apply full VSS plugin patch:
Shutdown TeamCity server
Open
<TeamCity Home>/webapps/root/WEB-INF/plugins/vss/
or<TeamCity Home>/webapps/root/WEB-INF/lib/
Back up
vss-support.jar
Replace
vss-support.jar
with new oneStart 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>/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>.exe
file to any folder.Open this folder, and run the program with
/log
switch. 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.jar
Inside the
tfs-support.jar
file, replace/bin/tfs-native.exe
with the new oneStart 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.jar
Replace tfs-support.jar with the new one
Start server
Capturing logs from TFS-native
Copy to some folder tfs-native.exe
. This file can be found under TeamCity temp
folder. The name would be TC-TFS-NATIVE-<some numbers>.exe
. Run this program with /log
switch. To get command-line parameters help, run the process with no parameters. Log files would be created under TEMP directory in TeamCity.NET folder. For each process new log file is created.
.NET runners
To patch .NET part of .NET runners:
Open
<TeamCity Server>/webapps/root/update/plugins/
Copy
dotNetPlugin.zip
to temp folderBack up
dotNetPlugin.zip
Extract
dotNetPlugin.zip
Replace contents of
/bin
folder with new files.Pack files again. Make sure there is no files in the root of archive.
Replace
dotNetPlugin.zip
file on the server.All build agents should upgrade automatically.
Run the builds.
To enable logging from .NET runners:
Open
<TeamCity Server>/webapps/root/update/plugins/
Copy dotNetPlugin.zip do
temp
folderBack up
dotNetPlugin.zip
Extract
dotNetPlugin.zip
Copy
/bin/teamcity-log4net-debug.xml
to/bin/teamcity-log4net.xml
You 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.zip
file 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.