InspectCode Failing in TeamCity (with Cake.net)

Answered

We are running a Cake build in TeamCity that uses the ReSharper add-in. Our build is failing when trying to run code inspections with the following message:

 

[11:46:18][Step 2/15] Running Inspections
[11:46:18][Step 2/15] Starting: C:\BuildAgent\plugins\dotnet-tools\bin\inspectcode.exe /config=C:\BuildAgent\temp\agentTmp\dotnet-tools-inspectcode.config
[11:46:18][Step 2/15] in directory: C:\BuildAgent\work\3ba9231c7589afd6
[11:46:19][Step 2/15] JetBrains Inspect Code 2016.1
[11:46:19][Step 2/15] Running in 64-bit mode, .NET runtime 4.0.30319.42000 under Microsoft Windows NT 6.2.9200.0
[11:46:23][Step 2/15] Custom settings layer is mounted. Used file C:\BuildAgent\work\3ba9231c7589afd6\MacLean.OneOffice.WebService.sln.DotSettings
[11:47:14][Step 2/15] Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 185.31.17.133:443
[11:47:14][Step 2/15]
[11:47:14][Step 2/15] --- EXCEPTION #1/3 [SocketException]
[11:47:14][Step 2/15] Message = “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond�
[11:47:14][Step 2/15] ExceptionPath = Root.InnerException.InnerException
[11:47:14][Step 2/15] NativeErrorCode = 10060
[11:47:14][Step 2/15] ClassName = System.Net.Sockets.SocketException
[11:47:14][Step 2/15] HResult = E_FAIL=EFail=80004005
[11:47:14][Step 2/15] Source = System
[11:47:14][Step 2/15] StackTraceString = “
[11:47:14][Step 2/15] at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
[11:47:14][Step 2/15] at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
[11:47:14][Step 2/15] �
[11:47:14][Step 2/15]
...
As you can see, the error seems to be due to InspectCode trying to access 185.31.17.133:443. Any idea why InspectCode is trying to access a remote server? Our internet access on our build servers is restricted.
1 comment
Comment actions Permalink
Official comment

Hello David,

I filed a new ticket to YouTrack https://youtrack.jetbrains.com/issue/RSRP-459276. 

ReSharper tries to download a json schema from the Internet to validate json files, but can't do so. Such exception is not handled silently in InspectCode as it should be. We are going to fix it in Command Line Tools 2016.2 release.

Thanks!   

Please sign in to leave a comment.