0

I have installed and configured an on-premise VSTS agent behind a corporate firewall. At first, the Nuget tasks were failing with connection related errors, but I fixed this using the HTTP_PROXY and HTTPS_PROXY environment variables. However, the Nuget Push task ( VSTSNuGetPush.exe ) is still failing with a connection related error, and I need to establish exactly how it expects proxy information to be configured?

From the VSTS logs, the actual error message is:

2018-06-21T11:28:25.6945523Z System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: 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 13.107.6.175:443

I'm not sure if it complicates things, but the first step in the release is a Nuget Tool Installer of 4.6.2 to ensure semantic versioning 2.0 is supported.

Any help greatly appreciated!

furkick
  • 423
  • 6
  • 18
  • Have you run your private agent with proxy specified ( https://learn.microsoft.com/en-us/vsts/pipelines/agents/proxy?view=vsts&tabs=windows)? – Marina Liu Jun 22 '18 at 05:20
  • Apologies for the delay in responding. Yes I did. The proxy doesn't need authentication, so the build agent was installed with just the proxy address: config --proxyurl . This, together with the environment variables was enough to get all Nuget operations, except for the push, working." – furkick Jun 28 '18 at 07:21

1 Answers1

1

There isn't any way to achieve this for now.

As a workaround, you can add a variable "NuGet.ForceNuGetForPush" in your build definition and queue the build with its value set to true. This will force the task to use nuget.exe to push the package which should read the proxy settings.

Eddie Chen - MSFT
  • 29,708
  • 2
  • 46
  • 60