In the last post of this series, we discussed reasons why we want to remove the human element from configuration and deployment. In this post we will create a Project inside Octopus Deploy, setting up a Deployment Process that will automate this process for us.
In this post, we will add Octopus Deploy to our Continous Integration pipeline that will allow us to automate configuration and deployments to x-number of deployment targets. With .NET Core being cross platform, I will show you how to set up targets for both a Linux and Windows based machine.
In the previous post to this series, we talked about our desires to become more predictable and reliable through automation. In this post, we start creating a Continuous Integration pipeline by setting up TeamCity to serve our build server needs.
This day and age, predictability and reliability are two of the most important words when it comes deployments. In this series, I am going to talk about how to add both predictability and reliability to your ASP.NET Core Continuous Integration pipeline using TeamCity and Octopus Deploy.