Allows using TeamCity as a Windows symbol server and source server.
Last successful builds available on the public TeamCity server and compatible with:
TeamCity Trunk (EAP releases)
<TeamCity Data Directory>
.NET Framework 3.5 must be installed.
Debugging tools for Windows as a part of Windows SDK must be installed.
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.
For step-by-step instruction, see a related TeamCity blog post.
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:
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.
Please ensure that Debugging tools for Windows as a part of Windows SDK were installed on the build agent.
If you believe you've faced a bug: Issue Tracker (project: TeamCity)
If you want to ask a question or discuss: Forum
The sources on GitHub.
Builds at the JetBrains public TeamCity instance.