Skip to main content

Azure DevOps Microsoft-hosted build agents and self-hosted build agents

What is a build agent in Azure DevOps? If you head over to one of your release pipelines and edit the tasks, you'll see "Agent job" and in that portion is an Agent pool. This agent pool is how you're deploying your code. If you're using a hosted agent, Microsoft is taking doing the care and feeding of the agent for you. Your hosted agent pool may change, whether you're deploying to OS X or Windows, OS X, or Linux.


Today we're going to create our own agent build with a Windows 10 build machine. Let's get started!

Pre-requisites;
1) Windows 10 (a VM if you have one would be great)
2) An Azure DevOps account
3) Admin rights to your Azure DevOps portal

The first thing we're going to do is head over to our Azure DevOps portal and create a new PAT token within our project. Click the icon with your initials on the top right of your screen and choose "security".


Next let's choose "New Token". For your scope choose "Agent Pools" and click create"


Now let's head over to our Azure DevOps homepage and choose "Organization settings". Choose "Agent pools" under Pipelines. Select "Add pool".


After that we'll need to download the agent, so move over to your VM if you are using one and sign into your Azure DevOps portal.

Once you're in your Agent Pools click on the "Agents" tab. You should see something similar to the screenshot below.



Download your agent in the Downloads folder of your user you're currently logged in as. After that we'll need to open up PowerShell to create our agent.

Run the following lines of code to create your agent;

mkdir agent ; cd agent
Add-Type -AssemblyName System.IO.Compression.FileSystem ; [System.IO.Compression.ZipFile]::ExtractToDirectory("$HOME\Downloads\vsts-agent-win-x64-2.155.1.zip", "$PWD")

Now we'll go ahead and configure the agent;

.\config.cmd

After that we'll have to type in our configuration information. Go ahead and do that similar to the screenshot below.


Now we're ready to run our agent. In PowerShell type;

.\run.cmd

Now if we head back over to our agent pools under our project, we should see our Windows 10 machine connected and it is officially an agent!





Comments

Popular posts from this blog

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …

Running PowerShell commands in a Dockerfile

As Docker continues to grow we are starting to see the containerization engine more and more on Windows. With the need for containers on Windows, we also need the same automation we get in Linux with Dockerfiles. Today we're going to create a Dockerfile that runs PowerShell cmdlets.
Prerequisites; 1. Docker for Windows
2. A code editor (VSCode preferred)

Let's go ahead and get our Dockerfile set up. Below is the Dockerfile I used for this post.

from mcr.microsoft.com/windows/servercore:1903 MAINTAINER Michael Levan RUN powershell -Command Install-WindowsFeature -Name Web-Server RUN powershell -Command New-Item -Type File -Path C:\ -Name config
As you can see from the above, this is a tiny Dockerfile. What this will do is install the IIS Windows 

Feature and create a new file in C:\ called "config".
You should see something very similar to the below screenshot;

Next let's create a running container out of our image. First we'll need to run docker container ls to

 get o…

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…