Package Re-deployment setting not working as expected

Legacy Execution
1

For one of our Octopus projects, we have Package Re-deployment (in the settings), set to “Skip any package step that was already installed.”
However, for a recent deployment we did to a QA environment, Octopus actually re-deployed existing versions of packages, which were already on Tentacles.
Why did this happen? Please let me know of any logs you may need.
We were running version 2018.5.6 when this occurred, and we have since upgraded to version 2018.8.11 to keep up-to-date.

Thanks.

2

Hi Jim,

Thanks for contacting us. To start with, the task log of that deployment that had the issue would be useful. Also the deployment logs of the deployments that first installed the package would also be handy.

Thanks

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.