When a package gets deployed with the IIS site/virtual directory configured, what steps does Octopus take during deploy? In the logs it only appears to copy the files to the destination folder. There is no mention in the logs or documentation whether the app pool or IIS site gets stopped/started. If we are copying files to the same folder, is it possible that a file lock would fail the process? Do we need to add steps to PreDeploy/PostDeploy to stop/start the site?
Thanks for your help!
-Steve.
Hi Steve,
In our default configuration, we change the path associated with the IIS site to point to a new version-specific folder. The change causes the site to restart, so should be relatively seamless in this regard.
Hope this helps,
Nick
Hi Nick,
Thanks for the response. It sounds like you aren’t explicitly stopping/restarting the site, correct? So if our site gets deployed to the same location each time (i.e. “C:\MySite”) instead of a version-specific folder, is it possible we run into issues with locked files if we don’t explicitly stop the site?
Thanks again,
-Steve.
Hi Steve,
Yes, I think you’re correct here.
Regards,
Nick