Bug Report: Creating a release touches ALL nuget packages

We are using the filesystem instead of a “real” nuget server. Our nuget packages are copied into this folder over the WAN from our build machine, which can take 2 or 3 minutes. During this time period, any attempt to create a release fails because the package file is locked due to the copy task.

This would be expected if trying to create a release for the same project, however during the copy operation for Project1, all other project releases also fail.

I assume this is because octopus is enumerating the packages to determine the newest version. This should be done with a read-only handle to prevent this issue.


This is now fixed in the 1.3.5 release.