Hi,
When we are using the “Transfer a Package” step in the transfer path, it is changing the name of the package. It is adding full path with the package name.
The TransferPath variable is: #{env:TentacleHome}\tempFolder\
Copied package ‘F%3A%5COctopus%5CITAAG-29_BuildServer%5CFiles%5CeLIMS-FGS.NugetExe.Deploy.1.0.0.nupkg’ to directory ‘xxx’
The project is the same on both our on-prem and ITAAG Octopus.
This does not happen on our on-prem Octopus but only happens on our ITAAG Octopus Deploy in Azure.
Sorry to hear you are having issues with the transfer a package step in your Octoups Azure instance.
To be able to look into this for you are you able to provide us with both the raw task logs from the working on-prem instance deployment and also your logs from your azure instance.
Once you have those are you able to upload them to a secure site we have here.
Are you also able to tell us what versions of Octopus Server you are running on the on-prem and azure instance.
Once we have this information we will investigate and report back with our findings.
Thankyou for sending over your logs, after reviewing them we noticed the Octopus Server for the deployment that is working is hosted on a Windows machine whereas the Server for the deployment that isn’t working is hosted on a Linux box.
We have tested the ‘Transfer a Package’ step on an Octopus Server instance hosted in a windows environment and it is working for us, however, when we test it from an Octopus environment hosted on a Linux box we encounter the same issues you are having.
This is a known issue documented here so we are aware of it.
The workaround for the moment is to just rename the file (which will be located in the area specified in the transfer path settings in the Transfer a Package step within your Project) after it has been transferred. You could create a separate step within the deployment to run a script and automate the rename.
I hope this shines some light on your situation, I will comment on the issue to let our team know another customer has been affected.
If there is anything else you need help with please don’t hesitate to get in contact.
Hi @clare.martin,
Thanks for the feedback. Sorry forgot to mention that the issue was on our Linux Octopus.
I will let our users know of the issue and workaround.