Building Your App in a CI Pipeline with Customized Build Servers (Private Agents)

This post details how to set up and use private build agents in Azure Pipelines (formerly Visual Studio Team Services) to overcome limitations of hosted agents, particularly for builds requiring custom tools or specific software versions. It highlights benefits such as dependency caching (NuGet, Maven), incremental builds, and faster machines. The post provides links to documentation for deploying agents on Windows, macOS, and Linux, as well as Docker images. It also emphasizes the use of Azure DevTest Labs for managing agent pools and controlling costs, and outlines the process of creating a Personal Access Token (PAT) for agent registration. Finally, it explains how to configure build definitions to use private agent pools and demonstrates how to verify that builds are running on private agents.
More from the Azure Pipelines Agent Operating System Support trail
- April Patches for Azure DevOps Server and Team Foundation Server
- CDN Domain URL change for Agents in Pipelines
- Announcing the General Availability of Managed DevOps Pools (MDP) for Azure DevOps
- Announcing Public Preview of Managed DevOps Pools (MDP) for Azure DevOps
- End of support for Azure Pipelines agents running on CentOS 6, Debian 4.9, Fedora 32, Ubuntu 16, macOS 10.14, and older versions