TFS2017.2 NuGet Recovery Task - ETIMEDOUT 93.184.221.200-00-0043

Question

I have several build definitions that use the "old" NuGet installer task to restore dependencies from our internal TFS feed (same collection); The channel URL is specified through the NuGet source parameter:

The recovery process works fine, as shown below:

Switching to a new version of a task causes a build failure:

How to disconnect connection attempt to 93.184.221.200-00-0043 due to the fact that the build agent does not have Internet access?

I am using TFS 15.117.26714.0.

Update 1

I copied the nuget.exe file to the c: \ nuget folder and added the folder to the PATH environment variable. Same result

Update 2

I copied the nuget.exe file to the folder C: \ B \ 1_tool \ NuGet \ 4.0.0 \ x64; result below:

Answer 1

Update 3 - Workaround

To trick the "new" NuGet task to find nuget.exe in the tool cache, you need to create a dummy file named x64.complete in the {agent work} \ _ \ NuGet \ 4.0.0 working folder and copy the nuget.exe file to the folder {agent work folder} \ _ tool \ NuGet \ 4.0.0 \ x64

Answer 2

Something seems to be wrong with the new version of the task. Usually he will not access api.nuget.org if you have disabled Use packages from NeGet.org .

Link to this similar problem: NuGet recovery task is not performed from Xamarin.Android template in TFS 2017 2 update

Also this related feedback (not yet resolved): The NuGet Push task fails and does not have a replay option

However, you can try to enable Internet access for your build agent, and then try again.

If this still does not work, try enabling system.debug at build time. Then record and share logs here for further troubleshooting.

As a workaround, you can use the old version for now.

Answer 3

In addition to the ds19 problem and the workaround (thanks!), We had a very similar problem with VS2017. In our place, servers, as a rule, do not get Internet access. With our upgrade to VS2017 and TFS2017 (Update 3), this rule should be relaxed.

We initially solved the build problem with ds19 Update 3 - Workaround , but it still left us unable to use anything other than nuget 4.0.0, as the Nuget Tool Installer task still gave a timeout error.

After working with MS, we advised us to add the CDN website (cs9.wpc.v0cdn.net) to our proxys whitelist. Once we have done this, we can also use the Nuget Tool installer task, in addition to restoring Nuget.

Answer 4

To make this work, we changed the environment of our build agents by adding

 http_proxy=http://wsa.arz.de:3128 https_proxy=http://wsa.arz.de:3128 

Hope this helps