Version 3 of the VSTS plugin has been rewritten and requires DotNet Core. DotNetCore was not a required by version 2 of the plugin, so there is a good chance that this error was generated because there are no agents with the DotNetCore capability.
You can confirm this by looking at the capabilities of the agents. The screenshot below shows an example of the capabilities for an agent.
I added the .NET Tools installer to install the latest SDK and it seems to be working, but it’s already installed on the build agent, so I’m not sure what the difference is.
The .NET Core Tools installer is convenient, but not required if you have .NET Core already installed. You can manually add the DotNetCore capability to agents, and point it to the locally installed version of .NET Core.
The screenshot below shows an example of an agent with the DotNetCore capability defined.
I had a similar issue, but only partly fixed by the adding the DotNetCore capability as described.
After the recent auto-update of the TFS/Octopus integration, by users complained that every release they got a message about missing DotNetCore as mentioned by the original poster. If they selected ‘Ignore’, then the release went through. This was with the version set at 2.*.
I installed dotnet core on my build server hosting my build agents, and added the DotNetCore user capability. This made the warnings go away.
However, if I change by release steps to use 3.* instead of 2.x, any Octopus steps fail with a timeout error:
2018-08-13T02:06:44.0227346Z ##[section]Starting: Package Mainline.PACK.OC.DMS
2018-08-13T02:06:44.0467570Z ==============================================================================
2018-08-13T02:06:44.0467570Z Task : Package Application
2018-08-13T02:06:44.0467570Z Description : Package your application into a NuPkg or Zip file.
2018-08-13T02:06:44.0467570Z Version : 3.0.165
2018-08-13T02:06:44.0467570Z Author : Octopus Deploy
2018-08-13T02:06:44.0476579Z Help : Version: 3.0.165. More Information
2018-08-13T02:06:44.0476579Z ==============================================================================
2018-08-13T02:07:08.3035242Z ##[error]Error: connect ETIMEDOUT 104.42.229.199:443
2018-08-13T02:07:08.3045214Z ##[error]Failed to execute octo pack command. connect ETIMEDOUT 104.42.229.199:443
2018-08-13T02:07:08.3275208Z ##[section]Finishing: Package Mainline.PACK.OC.DMS
If I switch back to 2.* again, the release to Octopus goes through.
Given dotnetcore is installed on the agent, why does this fail?
The VSTS plugin is being updated to remove the DotNetCore requirement. This means it will no longer be necessary to have this requirement configured on the agents; it is enough to have .NET Core installed.
I’ve upgraded, but still get the same problem with Octopack. The error log message says it is timing out accessing this IP:
error: connect ETIMEDOUT 104.42.229.199:443
That’s not an IP I recognise, and I am pretty sure not one on our network. I can’t ping it, and NSLOOKUP does not recognise it either. Is there something in the TFS Octopus adapter trying to dial out?
Any thoughts?
That IP address is most likely the plugin attempting to download the Octo cli.
The new version of the plugin does not have the CLI bundled with it (as version 2 used to), and so either requires the CLI to be configured manually, or automatically downloaded.