Applying Patches

Microsoft Visual Source Safe Integration

To apply the patch for vss-native.exe:

1. Shutdown TeamCity server

2. Open <TeamCity Home>/webapps/root/WEB-INF/plugins/vss/ or <TeamCity Home>/webapps/root/WEB-INF/lib/ folder

3. Back up vss-support.jar file

4. Inside vss-support.jar file, replace /bin/vss-native.exe with new one

5. Start the server

To apply full VSS plugin patch:

1. Shutdown TeamCity server

2. Open <TeamCity Home>/webapps/root/WEB-INF/plugins/vss/ or <TeamCity Home>/webapps/root/WEB-INF/lib/

3. Back up vss-support.jar

4. Replace vss-support.jar with new one

5. Start 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:

1. Copy the <TeamCity Home>/temp/TC-VSS-NATIVE-<some digits>.exe file to any folder.

2. 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:

1. Shutdown TeamCity server

2. Open <TeamCity Server>/webapps/root/WEB-INF/plugins/tfs/ or <TeamCity Server>/webapps/root/WEB-INF/lib/

3. Backup tfs-support.jar

4. Inside the tfs-support.jar file, replace /bin/tfs-native.exe with the new one

5. Start server

To apply full TFS plugin patch:

1. Shutdown TeamCity server

2. Open <TeamCity Home>/webapps/root/WEB-INF/plugins/tfs/ or <TeamCity Home>/webapps/root/WEB-INF/lib/

3. Back up tfs-support.jar

4. Replace tfs-support.jar with the new one

5. 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:

1. Open <TeamCity Server>/webapps/root/update/plugins/

2. Copy dotNetPlugin.zip to temp folder

3. Back up dotNetPlugin.zip

4. Extract dotNetPlugin.zip

5. Replace contents of /bin folder with new files.

6. Pack files again. Make sure there is no files in the root of archive.

7. Replace dotNetPlugin.zip file on the server.

8. All build agents should upgrade automatically.

9. Run the builds.

To enable logging from .NET runners:

1. Open <TeamCity Server>/webapps/root/update/plugins/

2. Copy dotNetPlugin.zip do temp folder

3. Back up dotNetPlugin.zip

4. Extract dotNetPlugin.zip

5. Copy /bin/teamcity-log4net-debug.xml to /bin/teamcity-log4net.xml

6. You may patch Log4NET config file if you need.

7. Pack files again. Make sure there is no files in the root of the plugin archive.

8. Replace the dotNetPlugin.zip file on the server.

9. All build agents should upgrade automatically.

10. 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.