We’re using Octopus 184.108.40.2068. Our Octopus server intermittently hangs when creating a release, and we think it’s related to the slowness of our file-share-based NuGet feed. We’re wondering if there is any workaround, or if we need to optimize our NuGet feed.
I think this is related to http://help.octopusdeploy.com/discussions/problems/468-octopus-ui-hangs-when-creating-a-release, which doesn’t look like it was resolved.
We use a file-share NuGet feed - for security reasons, we don’t allow the Octopus server to directly access the TeamCity NuGet feed. As a result, searches of the NuGet feed are very slow. When I click “Create Release”, the “latest version” box will remain in the “Loading” state for several minutes if I do nothing. To avoid this, we always type in a number in the “Specific Version” box. When we click “Create Release” on this form though, it is sometimes very slow even if we’ve entered a specific version number.
I’ve observed in Fiddler that there is an in-progress request to query the NuGet feed. The request to create the release comes after that ,and also remains in-progress. After several minutes, both requests complete. See attached sceenshot which shows the requests in progress. I’ve also attached statistics and captures for those two requests (#40 and #41) from Fiddler.
So it appears the “create release” request is stuck behind the request to query the NuGet feed. Is there any way to avoid this?
This happens maybe 30-40% of the time when we create a release. When it happens, we find that closing and reopening the browser solves the problem (just refreshing the page does not work).
If we wait long enough, both requests complete after several minutes. But that’s too long for us to wait.
Thanks for your help,