Is Octopus Deploy a Good Fit for Enterprise Deployment Automation?

I used Octopus a few years back, and my main concern was that it stores all its state in SQL Server, which adds extra costs. Plus, tracking changes over time is harder compared to Git-based solutions. It's decent for simple deployments but might not suit a containerized environment. We eventually transitioned to using GitHub Actions and Argo.

It's tough to give solid advice without knowing what you're deploying to. If it's anything besides Windows servers, I might recommend looking elsewhere. Octopus really shines in that environment, but it can struggle with other setups.

In my experience, Octopus works best for traditional deployments, often referred to as 'pet servers'. If you're dealing with modern applications like containers or ephemeral setups, it might not be the best fit. We switched from using it with EC2 to a more container-focused solution, because Octopus felt dated for that kind of infrastructure.

We moved the deployment part of our CI/CD from TeamCity to Octopus recently, and our experience has been largely positive. It's user-friendly enough that even our non-technical team members can promote builds without any headaches.

I've been using Octopus Deploy for several years and it's been a game changer for us. It handles deployments between different environments seamlessly and the features for managing deployment variables make maintenance a breeze. If you're facing complex deployment scenarios, I think Octopus would be a worthwhile consideration.