b Eduard Kabrinskiy - Azure pipelines self hosted - Kabrinskiy Eduard h1 Azure pipelines self hosted /h1 p youtube /p Azure pipelines self hosted a href="http://remmont.com" News headlines /a Azure pipelines self hosted h1 How to create and configure Azure DevOps Pipelines Agent /h1 h2 This article aims to help you choose and configure an agent for your CI Pipeline. /h2 p style="clear: both" img src="https://miro.medium.com/max/60/1*ykMbX6S1sexCUvsAldnXJw.jpeg" / /p h1 Introduction /h1 p When getting to know Azure Devops, the most difficult question is probably what steps you need to follow to make your CI Pipeline work correctly. /p p The crucial point in running the Azure CI Pipeline is the work of the Azure Pipelines Agent, which primary task is to establish a connection with the machine on which you want to run your DevOps CI Pipeline. /p p In this article, we will consider the following issues to help you choose an agent for your CI Pipeline: /p p ul li MS-agent vs Self-hosted agent /li li Advanced information about MS-agents /li li When to use MS-agents and when to use self-hosted agents /li li Configuring MS-agent /li li Configuring self-hosted agent. /li /ul /p p We will also take a look at the differences between the two agents to help you decide which one best suits your needs. /p p The figure below displays the Azure CI Pipeline workflow with a Microsoft-hosted agent and a self-hosted agent. /p p style="clear: both" img src="https://miro.medium.com/max/56/1*sSPmoLt9yxrWtoOa6cC7TQ.png" / /p p As you can see from the figure above, your pipeline has to be run in some kind of operating environment on some machine. A Microsoft-hosted agent and a self-hosted agent are bound to manage that pipeline execution. /p p In case of using a MS-Agent, the execution takes place in one of the ready-made operating environments in Azure Windows, macOS, or Ubuntu, which is deployed to Azure on the fly (provided as SaaS). /p p In case of using a self-hosted agent, the execution takes place on your physical or virtual machine (on-premise environment). /p h1 MS-agent vs Self-hosted agent /h1 p Thus, the primary difference between a MS-agent and a self-hosted agent lies in the fact that with a MS-agent, you get a ready-prepared virtual machine in the cloud with pre-installed operating system (Windows, macOS, or Ubuntu). You get a fresh virtual machine each time you run a pipeline. /p p If you use a self-hosted agent, the pipeline will be executed on your physical machine. /p p The table below shows the main comparative characteristics of the two agents. /p p style="clear: both" img src="https://miro.medium.com/max/60/1*ThIGx2TmrYl31fHq2-kLnw.png" / /p h1 Advanced information about MS-agents /h1 p You can get information about the pre-installed software or hardware for a specific MS-agent using PowerShell. For example, to receive information about software and hardware for MS-Agent and a Windows-2019 image, execute the following PowerShell script. /p p By executing the script, we get the following information about the virtual machine: /p p style="clear: both" img src="https://miro.medium.com/max/60/1*Gsyahi8l-6h7nURuK_M3qQ.png" / /p p As mentioned in the table above, some virtual machine images for MS-agent have a broad range of useful pre-installed programs. To find out what programs are pre-installed for a Windows-2019 image, we can create a PowerShell task with the following script: /p p After executing this script, we will see a list of pre-installed useful programs (this list is very long and the figure below displays only a part of it): /p p style="clear: both" img src="https://miro.medium.com/max/60/1*eZzSn-zD4-n2FRBzLNpcmQ.png" / /p h1 When to use MS-agents and when to use self-hosted agents /h1 p If you have a small project with source code that does not take much time to download, it also does not require a lot of time to compile the project and perform unit tests. In that case, Microsoft-hosted agent will be the best choice. As indicated in the comparison table above, the virtual machine image and all pre-installed programs (Visual Studio, Python, Chrome, etc.) for MS-Agent have the latest updates. After executing a pipeline, this virtual machine image is discarded and does not affect the execution of the subsequent pipelines. /p p However, if you have problems related to performance, accessibility, security, or other problems of that kind, it is better to settle upon a self-hosted agent. One of the important drawbacks of self-hosted agents is that you will have to keep track of operating system updates, as well as clear the disk of artifacts between pipeline jobs. /p h1 Configuring MS-agent /h1 p The setup of Microsoft-hosted agent is quite simple and straightforward: /p p ol li In the Agent pool /strong combo box, select Azure Pipelines /em . /li /ol /p p style="clear: both" img src="https://miro.medium.com/max/60/1*FxDrNUK4m92V35ji_FWJiA.png" / /p p 2. In Agent Specification /strong drop-down list box, select a required virtual machine image. /p h2 Azure pipelines self hosted /h2 h3 Azure pipelines self hosted /h3 p youtube /p Azure pipelines self hosted a href="http://remmont.com" Today's big news /a Azure pipelines self hosted h4 Azure pipelines self hosted /h4 When getting to know Azure Devops, the most difficult question is probably what steps you need to follow to make your CI Pipeline work correctly. The crucial point in running the Azure CI Pipeline is? h5 Azure pipelines self hosted /h5 Azure pipelines self hosted a href="http://remmont.com" Azure pipelines self hosted /a Azure pipelines self hosted SOURCE: h6 Azure pipelines self hosted /h6 a href="https://dev-ops.engineer/" Azure pipelines self hosted /a Azure pipelines self hosted #tags# replace -,-Azure pipelines self hosted] Azure pipelines self hosted#tags# /b b Kabrinskiy Eduard /b a href=http://remmont.com daily news /a