Octopus Deploy

We use the simplest Octopus use-case. We have multiple projects (websites, windows services, web apis) that we deploy to test and live servers using the octopus calamari client listener.<br><br>Everything just works as expected, and it makes deployments vanishingly simple. Also, the ease with which I can make a deployment, or re-deploy an old check-in means that rolling back is easy, which in turn makes all deployments much less stressful!<br><br>I cannot speak for the more advanced aspects of Octopus, but I cannot imaging working with a client on windows software and making live or test deployments without octopus. I would recommend it to any new client I meet.

We have used Octopus Deploy for many years now for our CI/CD (Continuous Integration/ Continuous Deployment) of roughly twenty projects. After a steep first learning curve and the initial investment of time and effort in the deployment projects, Octopus Deploy has saved us an uncountable number of hours in the past eight years. In all my career, I have seldom encountered such a versatile, powerful, and well-engineered software product. Support is also very responsive.

Octopus Deploy is used within our organization to provide continuous deployment to the development environment with manual gates for production deployment. Octopus Deploy is able to handle any environment or application, from very old legacy applications deployed to Windows Scheduled Tasks all the way to cloud-native function and service applications.

We use Octopus Deploy to deploy software across the whole estate and to ensure version control is adhered. Octopus has been great in allowing us to expand across the world and has become an important tool in our product cycle. It's a shame that their change in pricing structure for their cloud service is now pricing us out of continuing to use the service long term.

Before we used Octopus Deploy, we used to deploy our websites to our servers manually. This was a time consuming, error prone process. Many late evenings were spent in the office purely for website deployments. <br><br>We moved our deployment process into Octopus Deploy, automated and standardized every step, and have scaled the same process out to more websites as we've worked on more projects. We're even able to schedule the deployments so they can happen after hours without someone needing to work late.

We've been using Octopus to deploy our products to multiple environments customers and countries.

Octopus Deploy is helping to solve bottlenecks in getting code changes out to our Cloud Environments, as well as helping us automate our DevOps Tooling around database housekeeping, environment automation and general DevOps. The granular permissions model lets us empower developers without handing them the keys to the entire cloud castle, and the detailed auditing gives us the agility we need with confidence we can trace problems back to their source.<br><br>We're also planning for a small number of quirky use cases where the polling tentacle forms a useful bridge between PaaS out in the cloud and disparate services running behind NATs and Firewalls.

We use it for creating automating release deployments. It has very intuitive User Interface which makes it easy for less technical user like business personnel use. It has a number of plugins to support most of the devops tools to integrate with. What I personally love about Octopus Deploy is its proactive support. We post our queries, issues or requirement via email and they almost respond within hour.

CI/CD Pipeline is an essential component for DevOps practice and the overall Software Delivery Life Cycle. We use Octopus Deploy in the Continuous Deployment part in our CI/CD pipeline. It helps us deploy code changes quickly and reliably.

We primarily use Octopus Deploy to manage and push [the] deployment of our .Net (legacy) and .Net (core) applications. We also use it to automate tasks beyond code deployment. We have additionally begun integration with Kubernetes.

Octopus Deploy is used in our Information Technology department to automate the deployment of more than 60 applications, both internal and public-facing. Octopus Deploy allows us to be more consistent with how applications are deployed to four different lifecycle environments (Dev, QA, Stage, and Production). It allows us to have an easy fallback strategy if an application makes it to one of the environments and has an issue. It allows us to securely store sensitive information for these deploys (passwords, connection strings, keys, etc.) as opposed to saving these values in source code or environment variables. It allows us to easily and securely maintain the multitude of SSL certificates on the servers where we deploy. It saves the organization time and money by making this step of the dev-ops process more efficient and consistent. The deploys that were done with Octopus Deploy minimize and virtually eliminate downtime and its effect on our users.

At a previous company, someone outside of the company recommended Octopus Deploy (and Team City), and I recommended that to my manager. However, they decided to go with TFS, in spite of the huge cost, partially because they had credits with Microsoft that they could use to configure it. The Microsoft person didn't help much. We ended up with a horrible mess that was all broken in terms of the configuration - they could turn off someone's access, but the person could turn it back on, people could do things they shouldn't be able to do, permissions were hard to figure out, configuration to get it to build and deploy was painful, overall it was a disaster. Fast Forward, I started at my current company, and they used Team City and Octopus Deploy already (on Prem install of both). This worked out fantastic. We deployed eight machines at once. It was easy to get the deployments configured, super simple to set up the variables needed, and very, very easy to see what was deployed where. It took me very little time to spin up a new environment. This is currently being used in the cloud version - [for] which we have a paid license for. Speaking of which, awesome license system! 100% functionality up to 10 deployment targets, then a reasonable price per each.

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.

Octopus Deploy has been immensely helpful in helping reduce the 'Mean Lead Time for changes' and increase deployment frequency in our cloud environment. We use it to seamlessly push out new releases in our hybrid public-private cloud infrastructure. The runbooks are super helpful for orchestrating recurring maintenance tasks. Training new team members is a breeze as the UI is mostly intuitive.

Octopus Deploy is used for Devops team to deliver applications to different environments across the company and for customers. Octopus Deploy allows us to have an organization by projects and environments and having tenants configurations. Managing variables across all the projects and separate by environments is a nice of feature. Availability to create our own step templates for any need that we have for deployments.

We use Octopus Deploy as a deployment orchestration solution that allows us to easily and succinctly deploy critical corporate and scientific software in a reliable, repeatable, and automated way. it is being used by the software development team of [the] information technology services department to deliver software for the entire organization. It solves the problem of automated and reliable deployment orchestration for the organization and is an integral part of our process.

Octopus Deploy is being used by our DevOps group to automate the deployment of code. It's used for all automated deployments, which account for almost all of the total deployments, in the web development group. We do not currently employ Octopus Deploy to manage and deploy non-web-developed applications, however, it is used to manage items like certs and password resets.

We aim to have a light-weight and flexible deploy pipeline since we are a small startup. Octopus gives us a good deployment tool that isn't overly complicated. We use it to manage our deployment for all of our products. These include ASP.Net deployed to AWS EC2 hosts, Angular webapp deployed to EC2 hosts, published installers for desktop apps, and scripts to deploy new versions of ECS hosts. (Our builds are handled by Team City which integrates with Octopus nicely)

Software that is ideal to carry out the implementation of software or applications in development, so our company has decided to implement it as part of the software that can facilitate the work of developers in their department, since it has a very simple and easy to use, plus guarantees that everything that is implemented is what is really shown, this way you save time, avoid mistakes and work is much more effective.

Octopus Deploy is an interesting product that interacts with Chef and other programs to create group of servers in what is termed as 'tenants' which allows you to take specific actions on a particular subset of servers that are grouped by function or role. It can be used to deploy simple configuration changes or single scripts as well as laying down entirely new code. This has helped our company grow at scale without being overwhelmed with the sheer number of servers that we must maintain as we grow.

We use Octopus Deploy to handle deployment of about eight different applications across Development, User Acceptance Testing, and Production environments. Octopus ensures that we have consistent, repeatable results in our deployments through the automation it provides to the deployment process. By using Octopus, we can be confident that the same deployment package that we have been testing in our DEV environment is exactly what gets deployed to our UAT environment, and finally our PROD environment.

Octopus Deploy is used by our department to facilitate the deployment of many applications to many servers. Software deployment is difficult and humans make mistakes. Octopus Deploy makes it very easy to deploy applications to one or several servers with the click of a button. It has allowed us to deploy faster, more consistently, with fewer mistakes and less downtime.

As the DevOps Manager for a Microsoft Gold Partner I configure Continuous Integration Pipelines using Visual Studio Team Services (VSTS) and Octopus Deploy. Our Development and Business Intelligence Teams use Octopus Deploy to push custom applications and database changes to Azure IAAS and On-Premises Virtual environments. VSTS manages the CI pipelines while Octopus Deploy manages the granular details of the IIS and SQL Server deployment configurations. Octopus Deploy ensures we have consistent and reliable application deployments across Dev, Test, and Production environments.

Octopus Deploy is used as the primary tool for automated deployment for a host of applications built using as diverse applications as Microsoft BizTalk, Node.js, and SOA based applications. The automated deployments using Octopus has resulted in the quicker delivery of applications to Prod environments and eliminates the tasks that used to be done manually and were error-prone. This has helped the team focus on building better software and not worry about pushing the changes to Test or Production.