I’m having trouble with re-deployment of packages and I could not find clear information on how it is supposed to work:
Octopus 2019.6.8. LTS
- a package from an external NuGet feed is no longer present on the feed (for reference: FesadEssenceTransferService release 3.0.17)
- the version was deployed successfully earlier this year
- the retention policy of the lifecycle is at least 10 releases (no date!) and I can see the package in question in the tentacles cache of the server I want to deploy to (also in the correct environment folder):
- during redeployment Octopus states it is checking the cache but then tries to download the package from the feed, which fails.
I was under the assumption that Octopus would use a locally cached package in the tentacle cache and only download a package when it is not available in the cache. Especially with this deployment option:
Any ideas why this isn’t working? Can we force Ocotpus to prefer the tentacle cache over (re)downloading?
Edit: The more I am reading the more I suspect that the behavior I am looking for is not implemented. Can you give suggestions what we can do to avoid losing packages from ext. feeds that are currently installed?
Thanks for any hints,