Item: Octopus Deploy
Rating: 9
Author: Verified User

Use Cases and Deployment Scope

We use Octopus Deploy in IT to facilitate our CI/CD environment and structure. Octopus Deploy is used to define the environment and tenant-specific variables which are used for substitution in our config files as part of our deployment process. It allows us to, upon build completion, push new builds to all of our respective environments and not have to be concerned with environment variables or any manual deployment-related tasks. It's really an awesome piece of software that I'm not sure I've ever experienced a problem with, to be honest.

Pros and Cons

Variable definition and substitution.
Configurable deployment processes.
Automated deployments.
Deployment logging.

Sometimes it can become overwhelmed by parallel deployments.

Return on Investment

Totally positive - deployments are a breeze compared to past companies.
Parallel deployments can occasionally be problematic.

Key Insights

Do you think Octopus Deploy delivers good value for the price?

Yes

Are you happy with Octopus Deploy's feature set?

Yes

Did Octopus Deploy live up to sales and marketing promises?

Yes

Did implementation of Octopus Deploy go as expected?

Yes

Would you buy Octopus Deploy again?

Yes

Likelihood to Recommend

Well suited to development environments utilizing multiple branches with multiple releases. Teams can target specific release branches, which can be configured to trigger builds and Octopus deploys. Allows QAs to promote successful builds to higher environments and has permissions to limit who has the ability to promote.

Octopus Deploy - A Developer's Friend

Overall Satisfaction with Octopus Deploy