5 votesKevin Kelchen commented
I was directed to this suggestion by Octopus Support from an issue I came across:
When using a Custom Installation Directory, the copy of the package at the extraction location is left around after it has been copied to the Custom Installation Directory. The version in the Custom Installation Directory is the one that matters and is where the application runs out of; the version it was copied from in the extraction location is no longer useful. I would like a solution to automatically delete the copy of the package at the extraction location when using a Custom Installation Directory.
I think it's an important point to make because you could imagine that Octopus could get this feature where only the current release is retained and yet the copy of the current release's package at the extraction location could still be left to linger around when using a Custom Installation Directory.
6 votesKevin Kelchen shared this idea ·