Child pages
  • Symbol Server
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

General Info


Evgeniy Koshkin


Apache 2.0


free, open-source

Plugin Description

Allows using TeamCity as a Windows symbol server and source server.

Plugin Development Status



Last successful builds available on the public TeamCity server and compatible with:
TeamCity 9.0.x
TeamCity 8.1.x
TeamCity 8.0.3 (or later 8.0.x)

TeamCity Trunk (EAP releases)


  1. Put into the <TeamCity Data Directory>/plugins folder.
  2. Restart the server.

Build Agent(s) Requirements

Debugging tools for Windows must be installed on build agent(s) to make the plugin work.


TeamCity as a symbol server should be referenced by the following URL <TEAMCITY_SERVER_URL>/app/symbols. The exact URL is available on the Administration > Integrations > Symbol Server page.

To enable symbols and sources indexing, add the Symbol Files Indexer build feature to the build configuration. After that all PDB files published as build artifacts of this configuration and all related sources will be indexed.
The PDB files packed via TeamCity artifact publishing rules will be handled correctly.


The indexed data can be accessed in both modes: public (not requiring authorization) and authorized. The plugin uses standard authentication settings provided by the TeamCity server.

The following permissions are checked:

  • View build runtime parameters and data - while accessing symbols,
  • View VCS file content - while accessing sources.
    These are the default permissions of Project Developers.

If you are using the public URL to access symbols, you need to enable the Guest user login and assign the project developer role to the Guest to the Developers group.

When logging into TeamCity as a guest user, the corresponding permissions are checked to grant anonymous access to symbols and sources. If the guest user permissions are insufficient, all enabled Http authentication modules are applied and the user will be asked for credentials.

The access mode can be configured globally or on a project-level. Also, different access modes can be specified for the symbols and sources.


If you believe you've faced a bug: Issue Tracker (project: TeamCity)
If you want to ask a question or discuss: Forum

The sources in the Mercurial repository.
Builds at the JetBrains public TeamCity instance.

  • No labels