Thanks for reaching out. Sorry to hear you’re having issues.
It looks like you are trying to reference the location where the package is extracted in a later step. Assuming that is the case, here is what I recommend:
Either in a post-deploy script or a Run a Script step, you may define your output variable like the example below:
If I use a variable I set manually or per environment it works, but the output variable for some reason cannot be read.
Am I specifying the step name correctly as ‘DEPLOYMENT STEP’ or is there some mnemonic I need to use like DEPLOYMENT_STEP or some other secret handshake?
Thanks for following up! I’ll jump in here quickly as Adam is currently offline as part of our UK-based team.
When calling this output variable, you’d need to make sure the 'DEPLOYMENT STEP' part exactly matches the name of the step in your process that created the output variable. And the ProcessingPath is where you specify the exact name of the output variable that that step created. However I think there will be an easier way to call this value.
Octopus by default will create some output system variables during your deployment, where the one that I believe you’re requiring would look like Octopus.Action[Your Step Name].Output.Package.InstallationDirectoryPath. This means you shouldn’t have to worry about creating this custom output variable to store this value, and calling that in the next step.
In your step, there’s a #{} icon, where when pushed it’ll populate a dropdown showing all the available variables for that step. If you search for the above variable (InstallationDirectoryPath) and click it’ll insert it into the step with the correct syntax. This will look like the screenshot below.