Pushing packages to built-in repository randomly timeout

Hi,

I am using Octopus server 3.4.9 and using Teamcity plugin (3.4.2) to push packages to the built-in repostory in Octopus server.
Sometimes we got the issue pushing packages to server. It can be either a conflict after retried or a timeout. I understand the server may be busy at sometimes that may cause the issue, but I need a way to increase the timeout for the push operation. I don’t see any options in Teamcity to set the timeout. Is there a way I can set the timeout for this? Attached are the 2 screenshots of the error when it got conflicts and when it timeout.

Regards,
Tri

Hi Tri,

You are using Nuget.exe push which has a timeout variable -Timeout 500 where the value is in seconds.
Here is the corresponding documentation: http://docs.nuget.org/ndocs/tools/nuget.exe-cli-reference#push

If you are using Octopack with our OctoPackPublishPackageToHttp feature then you can also add a timeout via the NuGet Properties in the following way: "/p:OctoPackNuGetPushProperties=-Timeout 500"
Here is our OctoPack documentation: http://docs.octopus.com/display/OD/Using+OctoPack

Please let me know if you have any further questions.

Vanessa

Hi Vanessa,

Many thanks for you support. I did not know that we have that parameter. I’ll try and let you know the results.

Cheers,
Tri

Hi Vanessa,

I tried with the suggestions and it still not work. I added the parameter and as you can see in the screenshot, it is added to the push command, but it still fails sometimes. The log even says the timeout is only 100000 where it should be 500000.
Any ideas?

Hi Tri,

A 409 conflict is returned when you attempt to push a package version that already exists.
You can add ?replace=true to the end of the path where packages are uploaded to overwrite any packages that exist.
Here is the corresponding documentation: http://docs.octopus.com/display/OD/Push+a+NuGet+package+that+already+exists

Vanessa

Hi Vanessa,

Adding replace=true fixed the conflicts but the package push was still timeout and failed after a few attempts.
It looks like there was a bug and the timeout was not passed to the HTTP request as mentioned here http://help.octopusdeploy.com/discussions/problems/49247-timeout-when-pushing-to-octopus-deploy-server-using-octopack
I updated Octopack to 3.4.6 and it looks like it works.

Hi Tri,

Thanks for letting me know! Happy deployments.

Vanessa