Do you need to copy the NuGet package file, or just the files inside the package?
During deployment on the Tentacle there is a special variable available (Octopus.Tentacle.CurrentDeployment.PackageFilePath) which you could read in the Deploy.ps1 file, and then use that to copy the package to the file share.
We have plans to add a “NuGet publish” feature in future which would support publishing the package to a file share.
Did you ever create the “NuGet publish” feature or create guidance on how to perform this action? We have a very similar scenario where we’d like to “deploy” MSIs to environment-based shares for additional processing, such as GPO.
When you say ‘environment-based shares’, do you mean a shared folder like \\Shared\folder? If that is the case, then you could use a Custom Installation Directory which will allow you to deploy to a specified folder.
Let me know if that works for you. If that’s not what you’re meaning, could you expand a bit more by what you mean by environment-based shares and how are you currently deploying to them?
That gets me very close - by “environment-based” I mean \server\share<env> i.e. (\server1\drop\DEV or \server1\drop\PROD). Is there a way to access the environment variable? Or Project variables in these steps?
David - Actually my previous reply was tested in 3.3.27. Apparently those variables are not around in the latest version of 3.4. Let me get back to you on this after I ask the dev team. Might take until tomorrow as they are located in Australia.