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/
directory.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
directory. 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 directory.Run the program with the
/log
switch.
To get the command line syntax and options reference, run the program without any switch.
Microsoft Azure DevOps Server Integration
To apply a patch for tfs-native.exe
:
Shut down the TeamCity server.
Open
<TeamCity Server>/webapps/root/WEB-INF/plugins/tfs/
or<TeamCity Server>/webapps/root/WEB-INF/lib/
.Back up
tfs-support.jar
.Inside the
tfs-support.jar
file, replace/bin/tfs-native.exe
with the new one.Start the server.
To apply a full Azure DevOps plugin patch:
Shut down 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 the new one.Start the server.
Capturing logs from Azure DevOps-native
To enable creating logs from Azure DevOps-native:
Locate
tfs-native.exe
under the TeamCitytemp
directory. The filename format isTC-TFS-NATIVE-<digits>.exe
.Create a copy of the file in any other directory.
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
directory. For each process a new log file will be created.
.NET runners
To patch the .NET part of .NET runners:
Open
<TeamCity Server>/webapps/ROOT/WEB-INF/plugins/dotNetRunners/agent.
Copy
dotNetPlugin.zip
to a temporary directory.Back up
dotNetPlugin.zip
.Extract
dotNetPlugin.zip
.Replace the contents of the
/bin
directory 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 directory.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.