In this article, let's look at how we can configure and automate building ASP.NET Core code using Jenkins CI/CD freestyle pipeline
In this article we shall look at how we can automate executing test scripts on our fetched codebase after a build and generate a report out of it.
The final step in any automation job is to notify the results to the respective owners. Learn about how we can configure these automated mails feature in Jenkins.
So far we have seen how to setup a remote repository for a standalone codebase via git and then tieing up the same to a jenkins build job for automation. Next we have seen how we can fetch latest codeset from the repository, build to generate artifacts and run unit test scripts on the same using aspnetcore, xunit and such.
In a previous article, we were just getting started on automation server by installing and configuring a Jenkins automation server node onto a windows machine (Linux and Mac instructions added as well). In this journey, let's begin by setting up a Git repo and push all our local codebase into a central repo for the automation server to use.
Automation Servers are system nodes which perform predefined actions repetitively as a result of an event trigger or a periodic instruction with minimal or no manual intervention. And we shall look into setting up one such automation server which is also one of the most widely used tools in the market - Jenkins.