{"id":3418,"date":"2024-02-01T10:22:09","date_gmt":"2024-02-01T16:22:09","guid":{"rendered":"https:\/\/microsoftgeek.com\/?p=3418"},"modified":"2024-02-01T10:22:09","modified_gmt":"2024-02-01T16:22:09","slug":"setup-self-hosted-linux-agent-in-azure-devops","status":"publish","type":"post","link":"https:\/\/microsoftgeek.com\/?p=3418","title":{"rendered":"Setup Self Hosted Linux Agent in Azure DevOps"},"content":{"rendered":"\n

Let us learn how to create and configure a Self-Hosted Agent in Azure DevOps (ADO).<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

What is an Agent?<\/u><\/strong><\/p>\n\n\n\n

An agent is computing infrastructure with installed agent software that runs one job at a time.<\/p>\n\n\n\n

To build your code or deploy your software using Azure Pipelines, you need at least one agent. As you add more code and people, you’ll eventually need more.<\/p>\n\n\n\n

When your pipeline runs, the system begins one or more jobs. <\/p>\n\n\n\n

In Azure pipelines, there are two types of build agents:<\/p>\n\n\n\n

    \n
  1. Microsoft-hosted agents<\/u><\/strong> – This is a service totally managed by Microsoft and it’s cleared on every execution of the pipeline (on each pipeline execution, you have a fresh new environment).<\/li>\n\n\n\n
  2. Self-hosted agents<\/u><\/strong> – This is a service that you can to set up and manage by yourself. This can be a custom virtual machine on Azure or a custom on-premise machine inside your infrastructure. In a self-hosted agent, you can install all the software you need for your builds, and this is persisted on every pipeline execution. A self-hosted agent can be on Windows, Linux, macOS, or in a Docker container.<\/li>\n<\/ol>\n\n\n\n

    Pre-requisites:<\/u><\/strong><\/p>\n\n\n\n