OctoPack 3.4.1 issues with existing OctoDeploy Server

Legacy Uncategorised
1

I am experiencing issues with the latest OctoPack release.
When I go to run this command: “C:\bamboo-home\xml-data\build-dir\xxx\packages\OctoPack.3.4.1\tools\NuGet.exe” push “C:\bamboo-home\xml-data\build-dir\xxx\xxxl\obj\octopacked\xxx.2.0.2.24.nupkg” API-xxxxxxxx -Source http://localhost:8085/OctoDeploy/nuget/packages

It doesn’t seem to communicate. I get this message:
build 24-Aug-2016 11:44:56 Pushing xxx.2.0.2.24.nupkg to ‘http://localhost:8085/OctoDeploy/nuget/packages’…
build 24-Aug-2016 11:44:56 PUT http://localhost:8085/OctoDeploy/nuget/packages/
build 24-Aug-2016 11:44:56 InternalServerError http://localhost:8085/OctoDeploy/nuget/packages/ 92ms
build 24-Aug-2016 11:44:56 PUT http://localhost:8085/OctoDeploy/nuget/packages/
build 24-Aug-2016 11:44:56 InternalServerError http://localhost:8085/OctoDeploy/nuget/packages/ 63ms
build 24-Aug-2016 11:44:56 PUT http://localhost:8085/OctoDeploy/nuget/packages/
build 24-Aug-2016 11:44:56 InternalServerError http://localhost:8085/OctoDeploy/nuget/packages/ 94ms
build 24-Aug-2016 11:44:56 Response status code does not indicate success: 500 (Internal Server Error).

On the octo instance it shows in diagnostics as: Unhandled error on request: http://localhost:8085/OctoDeploy/nuget/packages/ by jasonhelman : Illegal characters in path.

Is there something specific that I would need to do to be able to use this latest package? Will using this and updating my server have adverse effects on the many projects that run older versions of octopack?

I have resolved it at the moment by just uninstalling the newest octopack and installing an older version I know works.

Server Info: 3.3.5

2

Hi,

Thanks for reaching out. Can you double check if you have a trailing / in the source URL in your octopack MSBuild parameter? If you have, please remove it and try once again.

Let me know how that goes.

Regards,
Dalmiro

3

Hi Jason,

This issue is caused by NuGet 3.4 and the way it sends the file over the wire, we fixed this incompatibility in 3.3.11. So you have two options really, install and use OctoPack version 3.0.71 or upgrade your Octopus server to the latest 3.3.x version which is 3.3.27 (or 3.4.0 if you want to go absolute latest).

Sorry for the inconvenience!

Thank you and best regards,
Henrik

4

Hi,

We are using 3.3.8, and I have encounter exactly same issue, is it solved in 3.3.8 too?

Even when I try to run same command from my local I get the same error

my nuget version is 3.4.4.1321

update

I download nuget 3.3.0 , now from my local I can push the package with no error,
So I was wondering how can I replace the octopus nuget.exe file with this version

5

Hi Reza,

No, this was fixed in 3.3.11.

Thanks,
Henrik