It looks like you can no longer obtain the directory of either the download package dir or the custom one. I don’t see it in the tooltip of 2.0 variables or the 1.6 Library mapping.
Am I missing something? Why would this be removed?
Hi Piers,
The second table on this page provides the variable names you’re looking for: http://docs.octopusdeploy.com/display/OD/System+variables
Let me know if anything’s missing.
Cheers,
Nick
Yup. I’m an idiot. Thanks!
Related to this…
Is there a reason why the $OctopusPackageDirectoryPath is not included in the variable sets that are provided for 1.6 mappings?
Am I correct in assuming that if it was in these mappings, it would work as is in projects and powershell scripts without any changes?
Hi James - as far as I can tell, you’re correct: mapping it to the new Octopus.Action.Package.CustomInstallationDirectory should work. You can do this by creating a new library variable set with the mapping to OctopusPackageDirectoryPath if you’d like to try it out (create a new release after including the variable set in your project). I’ll look into adding it to the default set.
Regards,
Nick
I think I just remembered why we don’t do this by default - in order to prevent an error during server-side variable evaluations, the added entry would have to be scoped to the action in question.