Estimated time to completion: 35 minutes
This task will guide you through the process of creating an infrastructure build and release pipeline. While the full project also creates a separate pipeline for the DSC Composite Resource module, the same principles apply so that we will concentrate on the build process of your IaaS workloads.
This task assumes that you have access to https://dev.azure.com
in order to create your own project and your own pipeline.
By the way: You can use the PowerShell module AutomatedLab.Common to automate your interactions with TFS,VSTS and Azure DevOps
Remember to check the prerequisites!
Whether you work with a test environment or at a customer location, you will need a repository for your infrastructure definitions - a project. Let's see how that works.
-
Navigate to https://dev.azure.com in a browser of your choice and log in.
-
Click on the
New project
button in the upper right corner and fill out the basics. It does not matter if it is a public or private repository for this lab.Note: New projects automatically use git as version control system.*
-
On the left-hand side, select Repos -> Files. The page says the project is empty. The easiest way to start is importing the project from GitHub.
Click on "Import" button. As the clone url, use https://github.com/dsccommunity/DscWorkshop without authorization.
-
Wait for a couple of seconds. The page will automatically refresh once the import job is done. All project branches, most notably
main
, have been imported. You should already be familiar with the structure from Task 1.
At the moment, this project does not do anything. However, you have started with one important component: Source code control for your infrastructure. From now on, every change to an infrastructure component needs to be committed, and every change can be accounted for.
Please continue with Exercise 2 when your are ready.