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

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…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

Pre-reqs;
1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.



Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…