Octo.exe timeout when creating a release with an external feed: can this be configured per-request or?

Wondering what the solutions might be for a timeout when creating a release with an external feed?
When I create the release manually from the feed, it can take up to 20 minutes to get to the package…
This error occurs after a couple of minutes when I use octo.exe programmatically.
Any suggestions?

Handshaking with Octopus server:http://octopus-url
GET http://octopus-url/api
Handshake successful. Octopus version:; API version: 3.0.0
Finding project: CondoTracking
GET http://octopus-url/api/projects
Finding deployment process for project: CondoTracking
GET http://octopus-url/api/deploymentprocesses/deploymentprocess-projects-14
Finding release template…
GET http://octopus-url/api/deploymentprocesses/deploymentprocess-projects-14/template
Resolving NuGet package versions…
Finding latest NuGet package for step: Deploy Files
GET http://octopus-url/api/feeds/feeds-3
GET http://octopus-url/api/feeds/feeds-3/packages?packageIds=CondoTracking
System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at Octopus.Client.OctopusClient.DispatchRequest[TResponseResource](OctopusRequest request, Boolean readResponse)
at Octopus.Client.OctopusClient.Get[TResource](String path, Object pathParameters)
at OctopusTools.Commands.CreateReleaseCommand.Execute()
at OctopusTools.Commands.ApiCommand.Execute(String[] commandLineArguments)
at OctopusTools.Program.Main(String[] args)
Exit code: -3


Thanks for reaching out. That timeout is not configurable unfortunatelly. I’m gonna need a bit more info to understand your scenario:

  • Is the external feed hosted on the same network using something like Lucene, Proget or the NuGet server? or are you using cloud solution like myget? This is important to understand the possible latency between the feed and the Octopus Server/Tentacles.

  • Could you send us the full deployment log so we can see the timings of each message? http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task



Hey Dalmiro,
Thanks for the response, but I have resolved my issue in creating
releases (using octo create-release) by adding the --packageversion
flag and giving the value of the package version which is known to the
CD system (Go).

This results in octopus deploy request bypassing the look up of the
package using the nuget api: this is were the timeout was happening.
This request was being made of a feed using NuGet Server, and the feed
had 100’s or 1000’s of packages and was requiring a considerable amount
of overhead.

I have also made a request of our operations folk to archive old
packages after some duration as best-practice (so we don’t see so much
delay if we create the release manually via the web console).
The use of the flag fixed the timeout when using automation.

Regards, Rick.

Hi Rick,

Thanks for posting your solution. Glad to hear you sorted it out.