For various audit reasons we have the retention policy on our lifecycles set to keep releases for 30 days. We use TFS build tasks to create release notes that contain the changeset and the associated user stories. This allows us to see what changes have gone into each package / release.
What we would like to do is to be able to keep the Octopus releases beyond 30 days but not retain the packages. I.e. we won’t be re-deploying the releases but would use them for audit purposes.
Am I correct in thinking this isn’t possible at the moment aside from manually removing the packages from disk?
Am I correct in thinking this isn’t possible at the moment aside from manually removing the packages from disk?
This is correct. If the release still exists, we consider it a candidate for re-deployment so we won’t delete the packages during the retention policy.
A possible approach would be to script this out like this:
Use the Octopus API to get your releases (filtering by date, version or however you like) and the packages used on them. You could use Octoposh and the command Get-OctopusRelease for that, which will return an object like this for each release: