Teamcity - OctopusDeploy: Create release

Hi Paul,

I am trying to deploy using teamcity using the Octopus deploy plugin and am getting an unusual error message when I try to publish to either the internal DNS name or the external one.
In this instance teamcity and octopus are on the same server

the error message is:

[11:41:56][Step 8/8] Octopus Deploy (4s)
[11:41:56][Octopus Deploy] Running command: octo.exe create-release --server http://theserver:10905/nuget/Feed/ --apikey SECRET --project SalesPlanner_App --enableservicemessages --version --deployto Staging --progress
[11:41:56][Octopus Deploy] Creating Octopus Deploy release
[11:41:57][Octopus Deploy] Octopus Deploy Command Line Tool, version 3.3.2+Branch.master.Sha.497e7f8ef2b193cd33560217bfecc38d721029a5
[11:41:57][Octopus Deploy]
[11:41:59][Octopus Deploy] Handshaking with Octopus server: http://theserver:10905/nuget/Feed/
[11:42:00][Octopus Deploy] Error from Octopus server (HTTP 404): OData method is not implemented.
[11:42:00][Octopus Deploy] Exit code: -7
[11:42:00][Octopus Deploy] Octo.exe exit code: -7
[11:42:00][Step 8/8] Unable to create or deploy release. Please check the build log for details on the error.

Any ideas what would be causing on OData error?


Hi Craig,

Thanks for reaching out. Paul is probably asleep right now (5am in Australia), so I hope you don’t mind me jumping on this one.

It seems like the URL you are using to reference the Octopus Server is not the right one. The URL http://theserver:10905/nuget/Feed/ looks more like a Nuget feed URL, but for Octo.exe you should be using your Octopus Server root url.

In the attached image the URL I use to reach the Octopus dashboard is http://ny-octopus1/app#/, so in that case I should be using http://ny-octopus1:[port] for the -server parameter in Octo.exe.

Let me know if that fixes your issue,

Hi Dalmiro,

Thanks for the help, I found a number of things that were wrong,

  1.  We were using an old version of octopus (2.x) – upgraded to latest version
  2.  API key was wrong – created a new one and changed in teamcity build step
  3.  Path as you noted below was wrong – changed in teamcity  build step

Now it all works like a dream, thanks again!



Glad to hear that! Happy deployments!