Hi Octopus team,
I’m getting this silence error related with the file hash.
Any suggestion ?
Thanks for reaching out! Could you please follow the below steps to send us a detailed deployment log? That should help us get a better understanding as what is going on.
1) Add these 2 variables to your project http://docs.octopusdeploy.com/display/OD/Debug+problems+with+Octopus+variables 2) Create a new release (so the new variables take effect) and deploy it. If possible skip as many steps as you can and only leave step we are troubleshooting in order to avoid the noise in the log. 3) Send us the raw log of that deployment http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task
Check the file attached,
ServerTasks-421.log.txt (43 KB)
The problem here seems to be that you are re-using the same package version (
1.0.0) for your packages more than once even though they have different contents, so when we try to find the right package on the Tentacle, we find find the wrong one (most likely one that you previosuly deployed).
Increasing your package version every time you build+push it would solve this issue. Is there a reason why you keep re-using the same version over and over?
I’m pushing the same package through TeamCity the reason for this is because is not practical to change the version just for a color change part of the same release.
I know the ideology is to always increase the number but I’m not a fan of having pointless versions on the history of the project.
In my opinion as is not possible to create a package with the same version then Octopus should be able to handle the fact that I’m replacing it for the current release.
I know a lot of people ask about “how to redeploy from teamcity using Octopus” this is basically what I did and sometimes it’s required and necessary.
As you pointed out, the ideology and best practice is to version your packages/releases, no matter how small the release is. We strongly stand behind the idea that even a simple app color change should have a different package/release version, as its not the same as the previous one with a different color.
That said, if you keep re-using versions like this your deployment should still keep working regardless of that warning you are currently getting.