Azure DevOps Configuration
This section explains how to configure Azure DevOps in AgileTest to trigger CI/CD pipelines remotely. Once configured, AgileTest can connect to your Azure DevOps repository and allow QA teams to run automated tests directly from a Test Execution issue without switching to Azure DevOps.
Firstly, click the New Azure DevOps Configuration button to reveal the configuration dialog.

A dialog will open for you to enter details.

You are required to fill in the details as follows.
Trigger Name: New trigger name for this configuration.
Organization: Your Azure DevOps organization.
Project ID or name: Your project name or Id. You should find these in Project Settings.
Pipeline ID: The ID number of your pipeline. You should find the number in the URL above the pipeline screen.

API version: As suggested, this number should be 7.1 → Please refer to this document for more details.
Pipeline version (optional): the pipeline version you would want to trigger.
Request body: This field allows the user to add any custom variables to send along with the triggering request. In most cases, you would not need it.
You can customize the Request Body with the AzureDevOps Rest API docs here.
Personal access token: the access token of the current repository. To get one, please refer to this document from Microsoft Create a Personal Access Token.
Additional Parameters: Additionally, we support extra parameters to map between your tools with AgileTest. They include:
Additional Params | Description |
FixVersion | Fix Version linked with the test execution |
Milestone id | The id number of a milestone. |
Revision | Source code version used in the test execution |
Test environment | A string contains a list of Test environments separated by “,” |
Test plan key | Test plan issue key |
Should you need any assistance or further AgileTest inquiries, contact our 24/7 Support Desk!