allow Tentacles to only retain the current release
Currently the Tentacle retention policies keep the currently deployed release, plus a user-defined number of older releases for the client.
Since retention policies don't run until after a successful deploy, this means that there's a minimum of 2 deployed versions on each Tentacle.
I would like it if Octopus would be able to clean up the prior release once it successfully supplants it.
Andrew Timson
shared this idea
-
Kevin Kelchen
commented
I was directed to this suggestion by Octopus Support from an issue I came across:
https://help.octopusdeploy.com/discussions/problems/70187-extracted-packages-linger-when-using-custom-install-directoryWhen 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.
-
Steve Sherwood
commented
I would definitely like this feature. We do not want older versions of our code deployed to our infrastructure. It is just a waste of space (especially with large deployments on minimal sized VMs). We should have the option of only having the version being deployed on the target.