Azure DevOps

You may well be aware of technology such as Helm and the creation of Helm Charts to manage applications on Kubernetes. It’s a great solution if you want your container to be consumed by the general public, but what if you want a reusable YAML file to deploy your services internally. We can easily have a template YAML file stored in a Git repository as part of Azure DevOps that can be used in our release pipelines and change placeholders based on variables set in our pipeline....

For this post, I will walk through the process of adding the ability to see repositories in GitHub Organisations to your Azure DevOps instance. When you are using Azure DevOps Boards, you have the choice of repositories to use to link your commits and pull requests back to work items you create in the Boards functionality. Adding a connection to GitHub It’s pretty easy to add your connection through to GitHub, from your project settings, simply click GitHub connections, from there you can then proceed click Connect your GitHub account....

To start this post, I want to assume you are already familiar with the process of creating Azure Functions. In order to follow this post, you will need to have an Azure Function already deployed (could be empty though) and a project in Azure DevOps which you have access to. Clone a test function If you don’t have any code available (I’m using C# functions in this example), you can clone a repository from my GitHub account if you wish to follow using the same code....

Let me start by saying fundamentally, Azure DevOps is a platform agnostic tool. You can use many different languages to deploy to many platforms. If you build in Node.JS, Python, Java, PHP, Ruby, C/C++, or .NET then you can use Azure DevOps. Likewise, if you deploy to Azure, AWS, GCP or even on-premise then you can use Azure DevOps. This makes it a really powerful tool. As expected, you can also deploy containers and push images to various different registries....