MetaData build step not available in TeamCity

I can’t find the runner type OctopusDeploy: Metadata when adding a new build step in TeamCity. We are running the latest version of the plugin (5.0.1+1) on TeamCity 2018.2.2. The other runner types are available (Create release, Deploy release, Pack, Promote release, Push packages

Hi @NikolaiMaric,

Thanks for getting in touch!

The issue here is that there is a newer version of our Teamcity plugin, you just haven’t been able to find it (which is entirely our fault, not yours). You can find the updated plugin here, sorry about the download experience.

If there is anything else I can help with please let me know,

Regards,
Alex

Yes, now the build step is available. Does’nt quite seem to work, though: I am not finding any metadata in Octopus after the release has been created. From the build log, everything looks ok:

[08:22:20] [Octopus Deploy] Running command: octo.exe push-metadata --server http://XXXXX --apikey SECRET --package-id XXXXX --version 2019.04.380 --metadata-file C:\TeamCity\buildAgent\work\9236a59338a79699\octopus.metadata
[08:22:20] [Octopus Deploy] Pushing package metadata to Octopus server
[08:22:21] [Octopus Deploy] Octopus Deploy Command Line Tool, version 6.2.3
[08:22:21] [Octopus Deploy]
[08:22:21] [Octopus Deploy] Detected automation environment: “TeamCity/2018.2”
[08:22:21] [Octopus Deploy] Space name unspecified, process will run in the default space context
[08:22:21] [Octopus Deploy] Handshaking with Octopus Server: http://XXXXX
[08:22:21] [Octopus Deploy] Handshake successful. Octopus version: 2019.4.2; API version: 3.0.0
[08:22:21] [Octopus Deploy] Authenticated as: XXXXX
[08:22:21] [Octopus Deploy] Pushing package metadata: “XXXXX”…
[08:22:22] [Octopus Deploy] Push successful
[08:22:22] [Octopus Deploy] Octo.exe exit code: 0

I also try to check if any metadata at all exist via the api (http://XXXXX/api/Spaces-1/package-metadata), but that only gives me a 405 error. Querying other things via the api works just fine.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.