Octopus Deploy Reviews

Most of our use cases are for continuous deployment. Basically, we would grab that package and deploy it to different adverse or intensive webs for our AKS spots. For continuous deployment, I'm using Octopus Deploy. 

The solution is very easy to set up. 

It is very stable. 

We can scale the product.

The UI is very intuitive.

It's hard to say what I would like to improve. There isn't anything specific that is missing.

There could be scope for more integration with other platforms. That said, for the kind of integration it has, it is good enough.

I've used the solution for a long time. However, I'm not sure for how long exactly. I've used it in this company and in previous companies as well. 

The solution is fairly stable. There are no bugs or glitches. It doesn't crash of freeze. It is reliable.

It is scalable and expands easily.

The whole organization is using Octopus. 

I haven't used support. Since it is on-prem, our tech support would manage to troubleshoot. There might have been instances where there have been some issues with the on-prem version that I don't know of. Our tech support may have touched base with the. However, I don't have that level of visibility.

We still used some bits and pieces of Azure DevOps for continuous deployment also. We still prefer Octopus. We have a history with Azure DevOps, however, it is not as good as we want our continuous deployment to be. 

It is easy to set up the product. That's likely the reason for its popularity. It's not a complex deployment. 

I'm not sure how many people deployed the product initially. 

Basically, we do not require technical people for deployment since we set it up once, and then it's literally one click. On a daily basis, we do not require any technical people in terms of maintenance.

The initial setup can be done in-house unless you have a specific level of complexity that you need to be executed.

I don't deal with licensing and cannot speak to the costs involved. 

This has always been our choice for continuous product development. 

I'm using the latest version of the product.

I would recommend the solution to others. It is one of the best options for continuous deployment. 

I'd rate it nine out of ten.

We're a DevOps team., and its use case is deployment. That's the only thing it does.

Our version is relatively recent.

Deployment is valuable. It deploys well.

You've got to jump through a few hoops to get some things configured, but if set up, you can do so many different things in it. So, there is complexity.

I've been with the company for five years, but they had it for a little while before I got there.

It's stable.

For us, it does everything we want. In terms of its users, there are two main users. There are two of us who handle the deployments.

It has been fine. We don't need to talk to them often.

I've used other tools that aren't dedicated deployment tools. I am simultaneously working with Microsoft Azure DevOps.

It was fairly straightforward. We moved servers a while back and upgraded. It was fine. It probably took a day. 

I don't know the exact cost, but it's not exorbitant. It may be a couple of thousand dollars a year or something like that. I'm not sure, but it's reasonable. We get value for money out of it.

It's a deployment tool. It does one thing, and it does it well.

I would rate it an eight out of ten.

We use this solution to promote deployments to different environments. We have test, speaking, pre-production and production environments. We use it to manage post-deployment or pre-deployment hooks and to run automated tests immediately after deployment to validate that everything works as it should.

The rollback feature has been most valuable. We can write scripts from scratch. Octopus maintains an independent package for every deployment. The fact that we can rollback deployments to a previous package if something goes wrong has reduced our workload. The access control allows us to divide complex levels of access control which has been a powerful feature for us. 

This solution could be improved by making it easier to divide variables in YAML file or JSON files. 

We have been using this solution since 2018.

It is a stable solution.

It is a scalable solution. 

Prior to using Octopus, we used Jenkins. We moved to Octopus because it is easy to use for our DevOps engineers. 

The initial setup is straightforward and for a simple use case, takes one to two days. 

Before deployment, I would advise getting the necessary processes ready before using the CI/CD flows provided by Octopus. In the course of setting up Octopus, you need to have a rollback script and scripts that handle the customization of Docker. Once these things are in place, it makes the setup faster. 

Depending on the load, we run a cluster multiple server deployment because as the number of engineers increases and the number of deployments increases, it can slow down the system. 

I would rate this solution a seven out of ten because it has served our use case very well.