Automated Publishing of ASP.NET Web API when publishing to Git

[winlonghorn]

At work, I am helping to orchestrate moving our small team to Source Control (especially on our Web Services). Does anybody know of a good way to setup an API to auto publish when changes are pushed to a remote repository in Git? As it is, we are looking at a minimum of 4 - 5 steps every time we need to make changes at the same time that another one of us is making changes. We want to simplify this process as much as possible. I have used Git in the past, but I am still fairly inexperienced with it. 

[adrynalyne]

  On 11/04/2019 at 11:55, winlonghorn said:

At work, I am helping to orchestrate moving our small team to Source Control (especially on our Web Services). Does anybody know of a good way to setup an API to auto publish when changes are pushed to a remote repository in Git? As it is, we are looking at a minimum of 4 - 5 steps every time we need to make changes at the same time that another one of us is making changes. We want to simplify this process as much as possible. I have used Git in the past, but I am still fairly inexperienced with it. 

Expand  

Azure Dev Ops has continuous integration. So does TFS. You could also look at something like Jenkins. 

[winlonghorn]

  On 11/04/2019 at 13:38, adrynalyne said:

Azure Dev Ops has continuous integration. So does TFS. You could also look at something like Jenkins. 

Expand  

Ok, thank you! I will take a look at that and see if it will fit our needs.

[+Kyle Subscriber¹]

There are a number of ways you can do this. 

Check out Hashicorp Terraform for managing deployments or you can have fun and deploy AWX (OpenSource version of Ansible Tower) which can watch Source Control. 

 

If you are using Github, there are number of CI/CD integrations you can use: 

https://github.com/marketplace/category/continuous-integration

 

If you are using Gitlab you can use Gitlab Runners which are my favorite ❤️

https://docs.gitlab.com/runner/

 

Most of these will require you to code your steps (in like yaml lol), but it's really easy to code after reviewing the documentation.