Set up an Azure Pipelines agent
To execute an Azure DevOps pipeline, you need an Azure Pipelines agent. This is a standalone program that’s similar to a Ranorex Agent. You install it on a physical or virtual machine, connect it to Azure DevOps, and can then pass pipelines to the agent for execution.
On this page, you’ll find out how to set up and start an agent. We’ll only cover what’s relevant for executing a Ranorex Studio solution through an Azure DevOps pipeline. For all other topics, please refer to the official Azure DevOps documentation.
In this chapter
Download an agent
To download an agent:
In the bottom left of your Azure DevOps project, click Project settings.
Click Agent pools.
Select an available agent pool. You can select from a hosted pool or from a local pool (default).
The following instructions assume a default local pool.
In the agent view that appears, click New agent.
Select Windows as OS, your OS’s architecture (x64 or x86), and click Download.
Unpack the downloaded .zip file to a folder of your choice.
The unpacked agent files.
Configure the agent
To configure the downloaded agent:
Double-click the file config.cmd.
Configure the agent as follows:
This is a basic userguide text with all paddings and margins set correctly. Just use all text styles H2, H3 etc… as you want. If you need to define Key strokes like CTRL do it like this here.
Paste the Azure-DevOps project URL from your browser’s address bar.
Press Enter to use PAT as authentication type.
In the Security menu of your Azure DevOps account, create a full-access PAT and paste it here.
The generated PAT is visible only once and can’t be recreated. Copy and paste it immediately after generating it.
Press Enter to select the default local pool.
Press Enter to confirm the agent’s name or change it.
Press Y if you have previously had an agent installed on this machine; press Enter if not.
Press Enter to confirm the work folder or change it.
Press N. The agent must not be run as a service.
Start the agent
To start the agent:
In the folder to which you unpacked the agent files, double-click run.cmd.
The agent starts, connects to the server, and idles until it receives a pipeline to execute.