In this post, I will dive a bit deeper into how to build your front-end assets for both ASP.NET and ASP.NET Core projects using TeamCity and how to appropriately pack those assets and publish them to Octopus Deploy, making them ready for your deployment.
In the last post of this series, we automated configuration of our builds and their deployments. In this post, we will talk about implementing front-end builds, databases and testing into our continuous integration pipeline, and publish build statuses to GitHub.
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.