I have 10-15 environments deploying at the same time using the same 4 process steps. When trying to access the output parameter Octopus.Action[Deploy files].Output.Package.InstallationDirectoryPath in step 4 (step 2 deploys a nuget package) this is randomly empty for some of (most of them) the environments, resulting in an error.
What could cause this? Is this because of scoping? And if so, how can I access this value per-environment-scope?
Thanks for reaching out. This could be for a couple of reasons. Could you please follow these steps to provide us with a deployment log so we can see the values of the variables during the deployment? This should help us knowing what’s going on behind the scenes.
Add these 2 variables to your project http://docs.octopusdeploy.com/display/OD/Debug+problems+with+Octopus+variables
Create a new release (so the new variables take effect) and deploy it.
Send us the raw log of that deployment http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task