Octopus Deploy

Pros: Octopus takes a complex challenge and simplifies it down to its simple elements. While you may outgrow the competitors and up-level to Octopus, I've never seen a piece of software too complex for Octopus.

Cons: It doesn't automatically integrate with the Roku store for deployment of streaming media channels. But neither do other products either.

Pros: I very much like the dashboard and space concept in octopus deploy, its so simple yet very relevant.

Cons: Sharing the resource like step template or feed etc. across space is something I feel would be very helpful from the platform team perspective.

Pros: While being extremely modular, and customizable, it is still easy to use.Integrates very well with our CI/CD

Cons: Understanding how environment, deployment targets, target roles can be difficult to understand without help, outside of the octopus documentation. When working with a space with lots of projects and environments, it can be difficult to find the right environment, project, and version number of the package i am looking for. Although I'm not sure that can be fixed, I'm not a UI guy.

Pros: The setup is straightforward. Learning curve is easy.

Cons: Its inability not to version control step templates.

Pros: Octopus Deploy is built for deployments, and it knows it. Octopus is very careful when adding features, and ensuring that everything is focused on a better deployment experience. The UI is easy to use, and provides guardrails to help people get started. The API, and custom templates allow admins to really customize processes to their liking.

Cons: While being focused on deployments only is one of the strengths of Octopus Deploy, when converting there was some extra work to separate existing CI and CD tasks. This created more up front work to get the pipelines running.

Pros: Octopus brings power to your DevOps Toolbox; Features such as lifecycles, variable configuration, release management, and the fact that the deployment system is built agnostic are why Octopus Deploy should be considered the go-to tool for complex deployments.

Cons: The Pipelines as code feature is pretty new and needs a little love to be great.As a professional, I do not like to use the UI to do my work, therefore the CLI, API and configuration as code needs to be 100% it will get there.

Pros: Octopus Deploy is a powerful and versatile deployment automation tool that streamlines the software release process. It is highly regarded for its ease of use and simplicity, with a user-friendly interface and intuitive workflows that make it easy to automate deployments across different platforms and environments.

Cons: Octopus Deploy is generally well-regarded by users, however some users have noted that the pricing structure can be a bit confusing. However, overall this concern is relatively minor and do not detract significantly from the value and effectiveness of the tool.

Pros: As the Product owner of a team using Octopus deploy, once I've completed testing, I can push to production myself. I can also easily see how many deployments there have been in the past weeks.

Cons: no complaints. I'm perfectly happy and will continue to use Octopus :)

Pros: Consistency of use over 7 years has proven OD to be a valuable tool to the organization. We have an 'admin' who runs the tool but our expectation is it more or less runs itself and allows us to focus on other technology issues.

Cons: Moving from a 'per server' to 'per seat' license has caused some initial issues, for instance we didn't used to renew every year due to not requiring upgrades, but now it's forced so that is getting extra scrutiny from the purchasing department. I've never found the reporting function in OD to be overly useful as I'd prefer it to be.

Pros: Versioning and configuration management

Cons: getting started is difficult for new on-boarders

Pros: 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.

Cons: 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.

Pros: 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.

Cons: 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.

Pros: We have been able to integrate Octopus Deploy with pretty much anything and everything we have thrown at it. We have all sorts of different types of deployments to various on-prem and cloud based targets. Even legacy based targets. We have not found a blocker that has stopped us from integrating our deployment requirements with Octopus yet. Octopus has ample amount of community based steps and first class steps out of the box that make it VERY powerful. Octopus is very customizable in how you handle deployments. Its really up to the end user to define what standard their business requires and Octopus makes it very easy to implement. For us we love step templates. Its re-usable code blocks that we can use at scale for thousands of deployments. No need to copy and paste the same code block into hundreds or thousands of deploys that are identical.

Cons: For the most part Octopus scales really well! We have over 13k projects with ~4k users in the tool and for the most part works fine. Though there are some inherent issues with UI/API performance when dealing with this many projects and users. They are working on these issues. But right now that's our biggest issue. Another topic of improvement would be around how step templates are version controlled. Right now all code in step templates is stored in the Octopus Database. I would love to see this moved to GitHub using the OCL language used for other parts of Octopus Config As Code. Lastly there are no good ways to template deployment processes besides cloning projects. I would love to see some sort of templating capability (similar to how TeamCity handles it). This would help greatly with scalability.

Pros: Config as code is awesome as is but if you have SOX requirements it’s essential

Cons: Upgrade paths sometimes are difficult but my organization is an edge case

Pros: The best thing about this software is that it automates the deployment process for your organization. It is very easy to set up and use and with this, you can save a lot of time. It will automatically manage your release cycles and does the deployments for you automatically.

Cons: There is no con to using this software it serves its purpose.

Pros: - Octopus Deploy does the "CD" part of the CI/CD pipeline very well. CI can be any tool to build the artifacts. Octopus can do the deployment part in different environments.- The deployment steps are under 'process' tab. It's possible to include python or bash script in the deployment step- You can host Octopus in your own VMs- You can choose where to run a project - in worker node or not.- Terraform has Octopus provider so IaC is easy

Cons: Unlike some other competitor products it's not great for both CI and CD, only CD is good.

Pros: I can automatically deploy packages from TFS to all the appropriate servers.

Cons: I can only set up one environment for automatic deployment within the tool. (There are ways to achieve this using Octopacks, though.)

Pros: We startet with continuous deployment with octopus, it was really easy do deploy our IIS Applications on mutiple environments. The deployments can easily be triggered from our CI plattform (TeamCity) and/or manual with user confirmation. In combination with Jira, every changes with each package are displayed during deployment making it easy to track when did any change reach the server

Cons: Despite there are a lot of build in steps, unfortunately a "rollback" step does not exist (or we haven't found it yet) thus implementing a rollback strategy must be done manually via script or manual. This could be a helpful improvement, to enable an automatic rollback in case any error occurs during deployment

Pros: Very easy to use and helps in deployment

Cons: Nothing as such. I couldnt find any con for this product

Pros: Friendly user interface, deployment log is easy to read.

Cons: runs slowly, other than that, it's pretty good to use

Pros: The interface, I think it is the easiest devops platform I ever used

Cons: I don't know exactly, everything if fine to me

Pros: Quick, accurate with logs, and can be timered

Cons: UI can be more clear to use or navigate