Starting December 5, 2025 (QMetry Test Management for Jira v4.15.1), the QMetry Test Management for Jira documentation moved from its location on Atlassian to a dedicated, standalone QMetry Test Management for Jira documentation page. For the latest updates, refer to GitLab Configuration.

Pre-requisites

GitLab runner should have been installed on the machine before triggering the build to GitLab. Refer to GitLab Runner | GitLab Docs for more details on GitLab Runner.
The gitlab-ci.yml file should have been created in Repository > Files in GitLab. The following is an example of yml file.

Generate tokens for Pipeline triggers

Follow the steps mentioned below to generate a token in GitLab. Refer to Trigger pipelines with the API | GitLab Docs for more details.

Steps:

1. Go to your project.

2. On the left sidebar, select Settings > CI/CD.

3. Expand Pipeline triggers.

4. Enter a description of the project’s trigger.

5. Click on the Add trigger button.

The Token gets added below.

Construct URL

The following is an example of constructing the URL to trigger a build in GitLab.

https://gitlab.com/api/v4/projects/<project_id>/trigger/pipeline

If your Project ID is 44922697 (as per the example shown in the image below), then the URL to trigger the build would be -

https://gitlab.com/api/v4/projects/44922697/trigger/pipeline

CI/CD Rule Configuration in QTM4J

The following are examples of triggering the build without parameters and with query parameters.

CI/CD Rule Without Parameters

CI/CD Rule With Query Parameters

After creating the CI/CD rule in QTM4J, you can trigger a pipeline job in GitLab.

The pipeline gets triggered successfully.