Hi all, In this blog series, I want to take you through the process of setting up Azure DevOps and using source control to provision and maintain a virtual server environment in Microsoft Azure. The technique used here can just as well apply to any other cloud or on-premises environment. The reason I am putting together is that I have found lots of material online about the subject, but I haven’t found any useful guides that explain the process from start to end.

Hi all, In this second part of the blog series, I want to focus in on Azure Boards and my use of it. In short Azure Boards is where I have all my notes for the project I am currently doing. I will describe the items I use when doing projects, but I won’t get into all the things you can use Azure Boards to do. Using Azure Boards also helps out a lot when more people are working together on the same project.

In this part of the series, I want to focus on the use of repositories. Repositories are where your code is stored, and in my case, this is often PowerShell code as I will also show in this series. Also, a part of repositories is the actual source control of your code, there are branches and pull requests. I will show how I am using this, and remember that I am an Ops consultant, so maybe developers are doing this very differently, but this seems to work for me at least.

In this part of the series, I will have a look at branches and pull requests. These two terms are essential to get familiar with since they are needed when working in teams on the code you are developing. I want to start with branches and what they are. The way I understand branches is that each time I need to work on an item on my boards, I want to create a new branch matching that board item.

Hi all, In this part of the series, I want to focus on the build pipeline. In short, the build pipeline will provide the rest of your pipelines with artifacts. Artifacts can be files, folders, or compiled code, and in my case here, it will be PowerShell files. As you will see in the series, I also use Pester tests to verify my code lives up to the demands I have.

Hi all, In this last part of the blog series about Azure DevOps for the Ops consultant I want to show you how to create the release pipeline for Azure deployments. The release pipeline is where the code written gets into the environment where it is used. Normally the first release pipeline would push to the development environment, but with all the different ways that companies use separate environment you will need to figure out how you want to do it.