Skip to main content
Skip table of contents

GitLab Configuration

This section explains how to configure GitLab in AgileTest to trigger CI/CD pipelines remotely. Once configured, AgileTest can connect to your GitLab repository and allow QA teams to run automated tests directly from a Test Execution issue without switching to GitLab.

Firstly, click the New GitLab 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.

  • GitLab Project ID: A string of your GitLab project id. To get project id from GitLab main page go to Projects → Open your project → Copy project ID.

  • Branch Name: A string of the branch on which you want to trigger the build.

GitLab field.png
  • Variables: 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. However, in some special cases, it may provide a way to collaborate with further setups in your GitLab pipeline.

You can customize the Variables with the GitLab Rest API docs here.

  • Pipeline Trigger Token: A string of your Pipeline trigger token. To create one please refer to this document from GitLab Create a trigger 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!

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.