Deployment to Custom Install Directory fails

Legacy Modelling
1

Hi,
I am using Custom Install directory to install the acceptance test assemblies. When I deploy a new release first time this step fails complaining the file path length restriction.
File path is constructed with fixed value (D:\Octopus\Apps) with other dynamic values such as package id, release number and azure region suffix.

When we check the installation directory to investigate why it is failing, we found that this step is creating a folder for the last variable (EUW) again and again.

So it is creating the folder D:\octopus\Apps\PackageName\1.0.0.1_alpha\EUW and keep creating the EUW folder in some sort of recursion until fails.

I have selected ‘Purse this directory before installation option’ to ensure latest changes are deployed all the time.

could you please help?

OctopusStep.png
OctopusStep.png1153×904 45.7 KB

2

Hi,

Thanks for reaching out! Could you please follow the below instructions and send us a full build log? That way we should be able to see why are variables behaving in such a way. Odds are there’s a recursive variable set in place that’s causing this.

1) Add these 2 variables to your project http://docs.octopusdeploy.com/display/OD/Debug+problems+with+Octopus+variables

2) Create a new release (so the new variables take effect) and deploy it. If possible skip as many steps as you can and only leave step we are troubleshooting in order to avoid the noise in the log.

3) Send us the raw log of that deployment http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task

Thanks,
Dalmiro