Octopus Deploy: Push Packages (Octopus 3.3 and TeamCity plugin 3.3.1 or newer) Push packages to the Octopus Deploy built-in repository, optionally using the TeamCity zip feature to create packages on-the-fly.
Deployment agent service. Run this installer on all of the machines that you plan to deploy software to. TeamCity Plugin.
A TeamCity plugin for Octopus! Published on: 19 Feb 2013.
One singe Octopus Server can control the deployment to all your environment so you can deploy to CI, staging and live all from one box. Finally, there is a TeamCity plugin for Octopus that can be deployed to control the publishing directly from TeamCity.
This plug-in allows TeamCity builds to trigger deployments in Octopus Deploy.
Out of this pain point, this plugin was born. It allows you to setup a single build that watches a specific Octopus Deploy project, and runs tests against the environment targeted when the project is deployed. TeamCity parameters are used to pass information about the environment...
This example uses the DLM Automation Build runner that's part of Redgate's DLM Automation TeamCity plugin.
That’s why we built Octopus Deploy. Where TeamCity is a build automation server, Octopus is...
It's supported as steps in both TeamCity and Octopus Deploy, and I get access to a lot of variables (Build number, version control hash and so on).
I found only one reasons why you will need Octopus Deploy. That reason is ~. Multiple servers deployment: If you have a lot of servers then Octopus tentacle comes in