Australian company Octopus Deploy offers their eponymous automated deployment and release management software that integrates with the user's preferred CI server and adds deployment & ops automation capabilities. Octopus Deploy enables developers, release managers, and operations folks to bring all automation into a single place. The vendor states that by reusing configuration variables, environment definition, API keys, connection strings, permissions, service principals, and automation logic,…
$12
TeamCity
Score 7.4 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
N/A
Pricing
Octopus Deploy
TeamCity
Editions & Modules
Cloud
Free 30 day trial
unlimited targets/users/projects
Server
Free 30 day trial
unlimited targets/users/projects
Enterprise
Starting at $18 per month
Enterprise
Starting at $18 per month
Server
Starting at $12 per month
Cloud
Starting at $12 per month
No answers on this topic
Offerings
Pricing Offerings
Octopus Deploy
TeamCity
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Octopus Server edition is available as a 30 day free trial on our unlimited tier for any scenario, including production, and commercial use. After the trial period ends you can keep your working configuration and upgrade to a paid license and continue deploying uninterrupted.
Octopus Cloud is an alternative that is hosted by us, and is also available as a 30 day unlimited trial. No credit card is needed to create a Octopus Cloud trial instance. You can convert the Cloud trial to a paid instance at any time during or after the trial period, and keep all of your instance configuration.
Octopus also offers an Enterprise tier which offers advanced features for teams at scale including, advanced high availability, insights & DORA metrics, ServiceNow & Jira Service Management integration, unlimited instances, 24/7 support & service credits, and a Customer Success Manager.
Volume discounts are available above 500 targets, and temporary bursting for certain scenarios is supported.
The ability to manage different stages and define a workflow is very useful for ops troubleshooting as well as deployment. You can see which version each environment has for each project, and promote or redeploy versions.
You can view deployment logs and dig deep into problems or long deployment steps.
Finding old releases can be a pain, and there isn't a good way to compare releases.
It does not really lend itself well to viewing what the content of a release is further than the version number. Ideally, you would be able to tie a deployment to the builds from the build server as well as specific commits from source control.
TeamCity is well suited for an organization using continuous integration, meaning you release code to production often, and an agile project management system. There are free versions available for small teams and enterprise versions available for large teams with many different builds. TeamCity is probably overkill for basic e-commerce or blog website builds that do not require much development after the initial launch
Many different platforms, languages, and operating systems are supported. You can deploy to your own server or the cloud. You can deploy to Windows, Linux, etc.
Many different "step templates" are included, which make it very easy to deploy what you want, how you want. Such as deploying over SSH, FTP, etc.
Support is very responsive and personable. You won't just be talking to a robot or a script. They will either solve your problem or understand it enough to solve it in a future release.
Their documentation is well thought-out and very helpful. I have found very few missing pieces.
Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.
Support for non-Microsoft applications needs to be improved to bring it on par with other comparable automation tools.
It doesn't yet provide integration options with other IT management tools like JIRA and HP Support to implement continuous delivery and true DevOps processes.
Support for AWS/Azure has been included very recently and it's not still very mature and feature rich and is expected to improve further in upcoming releases.
Some functionality feels slightly hidden in the menu system. For example: script modules are in the same menu as packages, where I feel that are not related entities. One is code for the deployment, the other is the thing that you are deploying...
Octopus Deploy is a software that runs very effectively, is easy to use, does not require such a high learning curve, provides the necessary tools to carry out the functions it offers, making it a very flexible software, it also allows that can be configured according to the needs of the user and provides integrations with other very advantageous tools since they are carried out in a very favorable way.
TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
Octopus Deploy support has always been there for us, even when using the free tier, we get responsive hands-on help. We haven't needed to use that level of support since the documentation is clearly written, and help is readily available within the interface itself. Using Octopus Deploy is a truly joyful experience.
Octopus Deploy was the obvious choice at the time, its strong .net support, robustness, ease of use, and integration into an existing process was a big plus. Also, Octopus Deploy was kind enough to give my organization a not for profit community licence. In addition, the product comes from a local Brisbane based company and it is always good to support local businesses when you can.
Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find the user experience of TeamCity to be much better, both from a look and feel, as well as from an out-of-the-box feature set perspective. The big selling feature of ADO is its native integration with Azure. TeamCity integrates very well with out-of-the-box .NET support and greatly simplifies our use of another diverse tooling outside of the Microsoft ecosystem.
Any automated deployment process will save your company a ton of money on testing and bugs. When you don't automate your deployments, you can't be certain that what you are moving between environments is the exact same code with the same or appropriate configuration. What you tested might not be what got deployed.
We've saved a lot of money using Octopus over the mostly manual process we were using before. We've removed a lot of the errors that come from manual, human intervention.
Octopus has also allowed us to accomplish more with fewer people. It is easy to bring new people up to speed on the deployment process, and we can be confident of success after very little training.
TeamCity was a key contributor to our organization's adoption of Agile.
TeamCity made it possible to KILL "It works on my laptop" conversations with Developers. If it does not compile in TeamCity - the project is not deployable. TeamCity's easy to use interface made it possible to quickly adopt a "Deploy Only from TeamCity" policy, further ensuring TeamCity Builds were the gold-standard for well-configured source code.
