"Deploying using NuGet provider" fails after 60 seconds

Hilmar van der Bijl's Avatar

Hilmar van der Bijl

05 Feb, 2015 10:12 AM

When pushing a relatively large nuget package (30MB) to our Octopus Deploy server, the build often fails at step Deploying using NuGet provider, with the message Process must exit before requested information can be determined.

I've clocked it and it looks as if a timeout is in place and set at 60 seconds. Whenever the push succeeds quicker than 60 seconds, it suceeds. Is my assumption about the timeout correct and is there a way for us to circumvent or enlarge this timeout? I know that the default timeout Nuget.exe uses is set at 5 minutes.

We are working on a newer and faster Octopus deploy server, but at the same time we're lining up a project that would push an octopacked nuget package of around 200MB, so the 60 second timeout may remain a bit too confining.

  1. Support Staff 1 Posted by Feodor Fitsner on 05 Feb, 2015 03:18 PM

    Feodor Fitsner's Avatar

    You're right - there is 60 sec timeout on running nuget.exe process. Will increase it.

    For now you can just replace NuGet deployment with your own nuget.exe command (which is in PATH) on build workers.


  2. Support Staff 2 Posted by Feodor Fitsner on 06 Feb, 2015 05:35 AM

    Feodor Fitsner's Avatar

    Hi Hilmar,

    We've just deployed an update with NuGet process timeout increased to 20 minutes.

  3. 3 Posted by Hilmar van der ... on 06 Feb, 2015 08:42 AM

    Hilmar van der Bijl's Avatar

    Thanks! Your support has been excellent, as always.

  4. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:53 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac