Hi,
Phew, today’s release seems to have messed with my head big time.
On a step I am setting the Destination Folder: C:\Websites\MySiteName\Web#{OctopusPackageName}
in the deployment the following is output:
2013-03-25 16:51:43 INFO [Copy] Extracting package contents to 'C:\Websites\MySiteName\Web\MySite.Web.BackOffice.UI’
2013-03-25 16:51:45 INFO [IIS] Updating IIS website named 'MySite.Web.BackOffice.UI’
2013-03-25 16:51:46 INFO [IIS] The IIS website named ‘MySite.Web.BackOffice.UI’ has had its path updated to: ‘C:\Octopus\Applications\Test205\Habanero.Web.MySite.UI\1.0.8011.8941’
Why if you specify the destination folder would the IIS set be updated to the one that is installed in Octopus Applications?
It seems counter-intuitive?
I was previously using the “OctopusPackageDirectoryPath” variable but this was behaving strangly today so I switched to the newer Destination option on the step.
Just a disclaimer - i’m only on day 2 of OctopusDeploy, but things seem strange.