Applying Patches

Microsoft Visual Source Safe Integration

To apply a patch for vss-native.exe:

Shut down the TeamCity server.
Open the < TeamCity Home >/webapps/root/WEB-INF/plugins/vss/ or < TeamCity Home >/webapps/root/WEB-INF/lib/ folder.
Back up the vss-support.jar file.
Inside the vss-support.jar file, replace the /bin/vss-native.exe with the new one.
Start the server.

To apply a full VSS plugin patch:

Shut down the 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 the new one.
Start 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 into 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>.exe file to any folder.
Run the program with the /log switch.

To get the command line syntax and options reference, run the program without any switch.

Microsoft Team Foundation Server Integration

To apply a patch for tfs-native.exe:

Shutdown the 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 a new one.
Start the server.

To apply a full TFS plugin patch:

Shutdown the 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 a new one.
Start the server.

Capturing logs from TFS-native

To enable creating logs from TFS-native:

Locate tfs-native.exe under the TeamCity temp folder. The filename format is TC-TFS-NATIVE-<digits>.exe.
Create a copy of the file in any other folder.
Run this program with the /log switch.

To get the command-line switches help, run the process with no parameters. Log files will be created in the <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/WEB-INF/plugins/dotNetRunners/agent.
Copy dotNetPlugin.zip to a temporary folder.
Back up dotNetPlugin.zip.
Extract dotNetPlugin.zip.
Replace the contents of the /bin folder with new files.
Pack the files again. Make sure there are no files in the root of the archive.
Create the <TeamCity Server>/webapps/ROOT/update/plugins directory.
Put dotNetPlugin.zip file into <TeamCity Server>/webapps/ROOT/update/plugins. All build agents will upgrade automatically.
Run builds.

To enable logging from .NET runners:

Open <TeamCity Server>/webapps/ROOT/WEB-INF/plugins/dotNetRunners/agent.
Copy dotNetPlugin.zip to a temporary folder.
Back up dotNetPlugin.zip.
Extract dotNetPlugin.zip.
Copy /bin/teamcity-log4net-debug.xml to /bin/teamcity-log4net.xml.
You may patch the Log4NET config file if you need.
Pack the files again. Make sure there are no files in the root of the plugin archive.
Create the <TeamCity Server>/webapps/ROOT/update/plugins directory.
Put the dotNetPlugin.zip file into <TeamCity Server>/webapps/ROOT/update/plugins. All build agents will upgrade automatically.
Run builds.

By default, all the log files will be stored in the <TeamCity agent>/temp/buildTmp/TeamCity.NET directory. Log files are created for each process separately.

Last modified: 28 July 2020