Skip to main content
This page describes legacy triggers. See Triggers for the current documentation.
If your repositories are hosted on GitLab.com or on a GitLab Enterprise Server instance with internet access, this is the recommended setup. If your GitLab instance does not allow outbound HTTPS connections, use the QA Wolf CI SDK instead.

Requirements

  • Access to a QA Wolf workspace with at least one environment configured
  • Maintainer access to the GitLab project

How to connect QA Wolf to GitLab

1

Connect QA Wolf to GitLab

Enable the GitLab integration in Workspace settings. You’ll be asked for a Group Access Token with the Maintainer role and API scope.Once connected, QA Wolf can set commit statuses and link test runs to GitLab commits.
2

Add the QAWOLF_API_KEY variable

Add QAWOLF_API_KEY as a CI/CD variable in your GitLab project under Settings → CI/CD → Variables. Add any other variables your pipeline uses.
3

Add the deploy notification to your pipeline

Add a job to your .gitlab-ci.yml that calls QA Wolf after your deploy step succeeds, replacing deployment_type and deployment_url with your actual values.
4

Verify the integration

Push a commit to trigger a deployment. Confirm a new run appears in QA Wolf under the expected environment.
Last modified on September 18, 2026