After upgrading to Octopus 2.4.1, steps that have powershell scripts against them (entered via the octopus UI) AND have a custom install directory entered (feature) no longer have the powershell scripts invoked during deployment. This has broken a few of our existing octopus project deployments…
2.4.1 steps with custom install folder and powershell scripts - those scripts will no longer run
Thanks very much for the bug report Darrell, and sorry about this. We’ll fix it in the next release:
assuming this was fixed so closing.