Thanks for getting in touch! You have a couple of options available to automate creating your releases in Octopus. The first way (and the way we strongly recommend) is to use our Team City plugin which is available on our downloads page. This is a great tool to easily integrate with TeamCity. Along with packaging and pushing your packages to Octopus, you can also create and deploy releases from it. It uses Octo.exe under the hood, so it's the most versatile approach. Check out our documentation on integrating Team City with Octopus. https://octopus.com/docs/api-and-integration/teamcity
The second way is to enable the Automatic Release Creation (ARC) feature to detect when a package is uploaded to the Octopus built-in repository. There are limitations to it, however, as it was designed primarily for people using older versions of TFS where their build configuration isn't easily changeable. You can read more about ARC in our documentation. https://octopus.com/docs/deploying-applications/automatic-release-c...
The auto deploy triggers feature you mentioned are a bit different, where they won't be able to detect when new packages are uploaded. They're machine-focused, where you can automatically deploy once a new machine has been created. Think auto-scaling, where you add more machines and you want your latest release to automatically deploy to them.
I hope this all helps! Let me know how you go and if you have any further questions along the way.
Thanks for following up! Your log snippet shows that the specified release doesn't exist, and we'll need a lot more info to help you troubleshoot what's going on.
1) Are you getting this error when trying to deploy a release from TeamCity?
2) Is your TeamCity configuration set up correctly, as shown in our documentation? https://octopus.com/docs/api-and-integration/teamcity#TeamCity-Trig...
3) Is this release being created in Octopus, and can you see it in the web portal? If so, can you successfully deploy this exact release manually in Octopus?
4) If your release isn't being created, can you attach your full TeamCity build logs? Otherwise, if your deployment is what is failing, can you instead attach your full deployment logs (as shown in our documentation)?
Any and all relevant information on your environment will be appreciated. :)
Changes included: 1 change
Change 4433 by vsisodiya (10 files
): *email notification for work item task*
5): This project references NuGet package(s) that are missing on this
computer. Use NuGet Package Restore to download them. For more
information, see http://go.microsoft.com/fwlink/?LinkID=322105. The
missing file is