or Create a profile
12 Jan, 2018 01:37 PM
I have got a pre-deploy, deploy and post-deploy powershell script that I want to run. They are located in a package, but unfortunately they contain some errors. Now instead of trying to fix the errors and commit some new code, I want to test out the new versions of these scripts by enabling 'Custom deployment scripts' in the octopus step. In this step all 3 the deploy fields now have different code.
The weird thing that is happening right now, is that the pre-deploy script is used from the Octopus step, while the deploy and post-deploy are still using the versions that can be found in the package.
I assumed that enabling the custom scripts option for this Octopus step, would ignore any scripts in the package. So for the pre-deploy this seems to be the case, but not the deploy and post-deploy.
I created several new deployments in Octopus with these changes, but it is like these changes are not picked up. Any ideas?
on 12 Jan, 2018 02:10 PM
Going through the logs I have spotted a problem. Looks like both the Octopus step scripts are running AND the custom scripts in the package. There doesn't seem to be a sequential order to it though.
For the pre-deploy script, the step version is executed first and than the package version.
For the deploy script, the packages version is executed first and than the step version.
Either way, is there a way so that it only takes the Step scripts and ignores the packages scripts?
on 15 Jan, 2018 03:56 AM
Thank you for getting in touch. I'm unsure why the scripts run in that order, but it looks intentional.
Unfortunately there is no way to ignore the packaged scripts. However it is something I intend to add this week. You can keep track of it here.
on 15 Jan, 2018 08:22 AM
Thank you for your reply. Looking forward to this option.
on 18 Jan, 2018 08:20 AM
Thanks for adding the variable: Octopus.Action.Package.RunScripts = false
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
A conversation has been started with the Octopus Deploy staff to resolve this discussion.
This discussion is private.
Only you and Octopus Deploy support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.