TeamCity Symbol Server plugin "Symbol Files Indexer" build feature returns "Directory is not found" file path error

I'm trying to set up TeamCity as a symbol and source server.  I've added the symbol server plugin to my server as well as added the "Symbol Files Indexer" build feature to my build.

Once the build starts, I see the following being logged:
[10:13:45]Source Server tools home directory located. C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\srcsrv

[10:13:45]Using Sources Server URL http://jefbuild01/app/sources/

[10:13:45]Publishing internal artifacts

The above suggests that the plugin and build feature are at least set up correctly.

However, towards the end of the build, I get the following output.

Running command "C:\Program Files\TeamCity\BuildAgent\plugins\symbol-server\bin\JetBrains.CommandLine.Symbols.exe" dumpSymbolSign "/o="C:\Program Files\TeamCity\BuildAgent\temp\buildTmp\symbol-signatures-1871151277539819701.xml"" "/i="C:\Program Files\TeamCity\BuildAgent\temp\globalTmp\dumpSymbolSign2984598251893093484.input""

[10:14:28]JetBrains.CommandLine.Symbols.exe ends with non-zero exit code.


[10:14:28]Stderr: System.IO.DirectoryNotFoundException: Directory is not found: es\TeamCity\BuildAgent\temp\buildTmp\symbol-signatures-1871151277539819701.xml    at JetBrains.Util.FileSystemPath.ThrowByError(WinError errorCode, String moniker, String additionalData)    at JetBrains.Util.FileSystemPath.OpenStream(FileMode fileMode, FileAccess fileAccess, FileShare fileShare)    at JetBrains.Util.FileSystemPathEx.ReadTextStream(FileSystemPath path, Action`1 FRead, Encoding encoding)    at JetBrains.CommandLine.Symbols.Program.LoadPathsFromFile(FileSystemPath inputFilePath)    at JetBrains.CommandLine.Symbols.Program.GetCommandToExecute(String[] args, String& error)    at JetBrains.CommandLine.Symbols.Program.Main(String[] args)

[10:14:28]Build finished

The issue seems to be that the option pairs being passed to the "JetBrains.CommandLine.Symbols.exe" command line tool are being quoted in addition to the value portion of the option, thus causing an issue.  I tested this by running the command on the server manually after removing the internal set of nested double quotes.

Any idea how to fix this?

1 comment
Comment actions Permalink

Thank you for filing We will answer in the issue.


Please sign in to leave a comment.