Excellent

Easy to configure and set up all your dev ops pipelines once and then invoke them over and over, to ensure consistent and completely automated deployments.

If you use their cloud offering with many targets it can quickly become quite expensive.

We have been using Octopus Deploy for many years now. It fits nicely into our fully automated CI/CD pipelines and allows development teams to move quickly.

The fact that Octopus is API driven allows us to easily automate everything in the deployment space. It allows us to have repeatable deployment and operations processes across all the phases of the lifecycle. Now with deployment steps as code, we can easily adjust the deployment steps per branch, which matches very well with our DevOps mindset. We are able to deploy many different types of projects with ease.

The biggest challenge we currently have is tracking down what project variables are used where. Between the deployment steps and runbook steps, it is sometimes challenging to find what is used where. The Config as Code feature starts to make this easier to track, once the runbooks are Config as Code enabled it should be much more manageable.

That I feel like it can do anything, or that I can do anything with it. The extensibility makes it feel like I can incorporate any deployment needs I have which is cool. We have a bunch of different applications and they're not all built the same, so it's nice to feel like there isn't any app we can't deploy with Octopus.

Sometimes it feels like I don't know what all the features are, or what features to use where. It can get confusing and sometimes I don't feel like the docs do a good enough job explaining this to me.

We have used Octopus Deploy to benefit all development teams and a number of infrastructure teams. In that they can control their own deployment processes and when they deploy. Infrastructure teams as well can create easy to use runbooks and provide them to other teams in a controlled manner to automate and provide consistent administrative tasks.

The ease of use from installation to new developer training. This tool thinks about every person involved. From the admin installing it, by giving them scripts to automate the install, to development teams using it with web ui built in help documentation. That and the support from Octopus Deploy, email, forum, Slack, calls when needed is top tier.

The only item of note is that although most deployment values are associated with a project, there are some that can't be restricted to certain projects. Some credential values can only be restricted by tenants or by environment. This is only a minor concern though as we have other ways of handling credentials.

I have been using Octopus Deploy for the past 9 years and have implemented it in over 4 different companies and have used its features extensively taking it to it limits :)

Kubernetes Deployment options and customization along with a lot of integration with different providers and tools

- Needs to Support Kubernetes CronJob deployment type (supported natively) - Needs to have a build in option to 'Wait' for Kubernetes Job type Deployments and read its exit code - Needs to support more Artifact Repos, such as AWS CodeArtifact - Cloud Agent needs to be 'faster' in general and ideally caches docker layers, we have deployments taking over 10mins, pooling/starting of the cloud agent takes time and also downloading the Octopus Tools Docker images takes very long on these agents (we're not using any custom one)