Tell me if you heard this one before, I'm a recovering developer. I spent most of my adult life writing code. I love everything about it. That is until I had to deploy all that code I just wrote. Everything about it was painful!! When we decided to rewrite eSP in 2018, one of the areas I desperately wanted to over haul was how we deployed and packaged all the code we wrote. In 2018 we set off to build a best in in class deployment automation pipeline. We started our journey like most do with the selection of our task/issue/code platform. We had used the Atlassian stack for the older versions of eSP. But with the change to .Net Core 1 we decided to give the Microsoft stack and Azure DevOps a try.With DevOps and Octopus Deploy what used to take us hours to do can be done in minutes. Our average commit to QA testing has dropped from two weeks to twenty minutes. Back in the stone ages we would update the QA environment at the end of every sprint, now we do that with every commit. The deployment automation grew from a massive project with 50 steps to what it is today. Today we have everything broken down into self contained portions of that application that can be deployed individually as needed or through the orchestration project that deploys the entire application.We've added to our toolset along the way, from using EF Core migrations to RedGate SQL Change Automation as our database automation tool. RedGate integrates wonderfully with Azure DevOps and Octopus deploy. We've also added Docker containers to the process to build the next advancement in eSP.Current ProjectAt the moment I'm working on a massive shift to the cloud. For the cloud operations we've selected Azure AKS and kept the tooling the same, Azure DevOps, RedGate SQL Change Automation and Octopus Deploy.Most of the changes for the cloud are in Octopus Deploy or AKS. I've created new projects and deployment pipelines that integrate with Azure AKS. We now have a fully operational test cloud up and running. We can now setup a new customer in the cloud in under 30 minutes. Way back in 2017 we would tell customers 90 days to spin up a instance, 90 days it just crazy now.At the moment its just a test cloud as sales and marketing work their magic. I can't wait to hear customers feedback as soon as the beta opens! If your interested in the beta please contact: sales@e-Ventus.com.