TABLE OF CONTENT
Today I’m going to talk about self-hosted build agents.
After reading this post you will be able to host your own Windows or macOS build agent (we’ll run it on your laptop) and use it to execute AzureDevOps Pipeline.
It’s common to run different steps of your build and deployment on different machines. You build steps can have different requirements, for example:
- Compute and disk space requirements
- Software requirements (SDKs, OSs)
- Location (geolocation, network isolation)
AzureDevOps and GitHub support two differet types of build agents:
- GitHub Hosted (Microsoft Hosted)
From now on I’m going to talk about Azure DevOps, but the same patterns and ideas apply to any other modern build systems.
Microsoft-Hosted Build Agents #
Microsoft-hosted agents are convenient, because this is probably the simplest way to execute our build pipelines.
Managed agents have these advantages:
- maintenance and upgrades are taken care of for you.
- every pipeline run gets a fresh VM (it’s discarded after use)
- consumption based billing
The agent choice is generic and broad enough to cover most of the common use cases.
Microsoft-hosted agents that run Windows and Linux images are provisioned on Azure general purpose virtual machines Standard_DS2_v2. These virtual machines are co-located in the same geography as your Azure DevOps organization.
Agents that run macOS images are provisioned on Mac Pros. These agents always run in US and Europe irrespective of the location of your Azure DevOps organization.
All of these machines have 10 GB of free disk space available for your pipelines to run.
- Microsoft-hosted agents run on Azure public network, they are not assigned public IP addresses. That means external entities cannot target Microsoft-hosted agents.
- You don’t have to worry about security issues when running code, frameworks or containers downloaded from Internet.
However it’s important to understand the limitations
- Diskspace is limited
- No way to RDP or SSH to the build agent and troubleshoot the build
- No way to upgrade the hardware
- macOS agents run in US and Europe only, so you may have issues with data sovereignty
- No way to join machines directly to your corporate network
- No way to pre-install custom software (other than through tool installer tasks)
- No control over software upgrades, cannot use legacy SDK’s ect
- No control over the waiting time (it depends on the load)
To address these issues Microsoft (and other vendors) allow us to use self-hosted agents.
Self-hosted agents #
Self-hosted agents are the agents which you set up and manage on your own.
- macOS agent
- Linux agent (x64, ARM, RHEL6)
- Windows agent (x64, x86)
- Docker agent
Managed agents will run in a cloud, and won’t have access to your private network, however self-hosted agents can be deployed into your VNet, behind the corporate firewall.
Self-Hosted agent #
Since I’m running Windows right now, I’ll show you how to set up a Windows agent.
There are several steps which I need to complete in order to set up a build agent:
Obtain a personal access token (PAT) #
and create a PAT with these scopes
create a new pool
create a new agent
Download the agent and configure it
PS C:\> mkdir agent ; cd agent PS C:\agent> Add-Type -AssemblyName System.IO.Compression.FileSystem ; [System.IO.Compression.ZipFile]::ExtractToDirectory("$HOME\Downloads\vsts-agent-win-x64-2.179.0.zip", "$PWD")
If everything is good, you should be able to see your new agent:
We can create simple pipeline
And verify if it’s running on my PC
As you can se we have our pipeline running on my computer. This means I can use my own hardware such as GPU or devices connected to my laptop. Also I have acces to internal network, printers and whatnot.
In reallity you would probably run the self-hosted agent on VM or a dedicated phisical machine.
Important notes #
It is a bad practice to configure your self-hosted agents for public repositories. Keep in mind that anyone can create a fork of your repository, modify a pipileine and execute code on you machine. It’s ok for a test, it’s ok to configure it for private repo, but please be careful, and don’t forget to shut down the agent when you don’t need it anymore.