From big bang releases to deployment four times per week

When I started working for this company back in 2003 we used to upgrade our production servers pretty regularly every six months. A couple of times we decided to go nine or twelve months between upgrades, and in one very particular instance when we had to replace a core data storage system we went a whopping twenty months between releases.

Today we release to production four times per week (Monday through Thursday).

So, what happened? And perhaps as important – why? Continue reading “From big bang releases to deployment four times per week”

Evolution from standard Octopus usage to large scale On-Premise deployments

Background

About 3-years ago, we started our move from deployment using MSI to using Octopus Deploy. The MSI setup was hard to maintain and manual to deploy/install. Octopus seemed like a good fit for automated deployments. For more than 1 1/2 years, we have now been running all our deployments to both test and production environments using Octopus.

Confirmit Horizons is a quite large application/platform that consists of 60+ services, API’s and web applications. The deployment process in Octopus has about 80 steps.

At the same time we have also stared our journey from a monolith to microservices so the number of services and API’s are constantly growing.

On our main Octopus server, we have about 40 environments. Most are test and staging environments. Our three On-Demand environments in US, UK and Australia are also defined on this server. There are a total of about 300 machines/tentacles in these environments.

We also have an Octopus test server mainly used for development/testing of microservices. It has about 60 projects, 10 environments and 50 machines/tentacles.

So far, all is standard usage of Octopus.

Challenges

We have a set of challenges that are not solved by standard usage of Octopus. Continue reading “Evolution from standard Octopus usage to large scale On-Premise deployments”