We’re using the on-prem version of Octopus for releasing ASP.NET websites and have encountered a strange problem in the last months.
Sometimes (like 1 a out of 3) when the site startup after a release the old process still have locks on some files (ie a disk cache file that is used by Umbraco CMS), restarting the app pool manually solves this but it’s not something that we would like to do.
So I’m wondering if there is any way around this? Does octopus just change the path to the website during the release or does it in some way restart the app pool? If not, can this be configured?