Use a local cache for packages when promoting between environments
If you use environment in a "progressive" fashion, you deploy the version to an environment, then promote the package to another one, etc.
Currently, octopus download the nuget package for each step, beside the fact that it should not have changed.
We have our nuget feed hosted near our build server (inside organisation) and octopus portal outside. Our package is 20MB, and it takes 5 minutes to upload it to octopus. We don't want to move our nuget feed outside, as we deploy as a build step, and there are more builds than octopus deployments.
Octopus portal could use a local cache for nuget packages, so promotion will only deploy the local package to the tentacles, preventing a round-trip with our nuget feed.
Octopus could also delete old packages as soon as the release is not visible anymore in any environment.
Leblanc Meneses commented
maybe adding a checkbox to the release screen next to Force re-deployment.
* Force Download of Packages (default unchecked)
If not checked it will try to use the cache unless that cache is not found. A force download of packages is only useful in the beginning when creating the ps1 files initially (debugging).