GitLab
AIO Tests now supports direct integration with GitLab, enabling seamless connectivity between your test management workflows and your CI/CD pipeline. This allows users to trigger pipelines and fetch results directly within the AIO Tests interface, eliminating the need to switch between tools.
To get started, you can configure your CI/CD system to link your GitLab pipelines with AIO Tests. Once configured, you can create AIO jobs that map directly to your GitLab pipelines, enabling automated execution and result retrieval.
In this documentation, you’ll understand:
Steps to Set up a CI/CD System
Step 1: To set up a CI/CD system, simply click on the Cycles option in the top bar menu.
Step 2: On the Cycles page, click on the CI/CD Integration button.
Step 3: Once you click on the CI/CD Integration button, the CI/CD Integration modal window will appear on the screen. Click on the Setup CI/CD System button.
Step 4: On the Setup CI/CD System modal window, select GitLab from the Type drop-down list, tick GitLab and enter your Name and Namespace into their respective fields.
To set up a GitLab Dedicated system, users need to enter the Host URL into the required field.
Step 5: Finally, click on the Save button.
Steps to Set up Credentials
Once your GitLab CI/CD system is created in AIO Tests, the next step is to add system credentials to enable access to GitLab pipelines.
AIO Tests uses GitLab tokens to authenticate and access pipelines. GitLab supports the following token types:
Personal Access Token (PAT)
Group Access Token
Project Access Token
Trigger Token
You can choose the appropriate token type depending on your organisation’s access requirements and automation setup.
Personal Access Token (PAT)
A Personal Access Token is created by an individual user and can access all projects and groups available to that user. This is the most flexible token type and is recommended for initial setup and validation.
Steps to Generate:
Click on your avatar in GitLab
Navigate to Edit Profile > Access Tokens
Enter the required token details
Select the api scope
Click on Create token
Copy the generated token and store it securely
Group Access Token
A Group Access Token is created at the group level and can access projects within that group. This is useful for automation within a specific organisation or team.
Steps to Generate:
Navigate to the required GitLab group
Go to Settings > Access Tokens
Enter the required token details
Select:
Role: Maintainer
Scope: api
Click on Create token
Copy the generated token and store it securely
Project Access Token
A Project Access Token is created at the project level and can access only that specific project. This is commonly used for repository-specific automation.
Steps to Generate:
Navigate to the required GitLab project
Go to Settings > Access Tokens
Enter the required token details
Select:
Role: Maintainer
Scope: api
Click on Create token
Copy the generated token and store it securely
Trigger Token
A Trigger Token is used only for triggering pipelines and cannot access other GitLab APIs.
Steps to Generate:
Navigate to the required GitLab project
Go to Settings > CI/CD
Expand the Pipeline Triggers section
Click on Add trigger
Enter the required details and create the trigger
Copy the generated trigger token and store it securely
Adding Credentials in AIO Tests
Step 1: To add credentials in AIO Tests, simply click on the Gear icon and select the My Settings option from the drop-down menu.
Step 2: Click on the CI/CD Credentials option in the sidebar menu.
Step 3: Click on the Add System Credential button and select GitLab from the drop-down list.
Step 4: Select the desired CI/CD system and enter the API Token into the API Token field.
Step 5: Finally, click on the Save button.
Trigger tokens are supported only while triggering jobs. Setting up the integration requires a Personal Access Token (PAT).
Steps to Configure a Pipeline
Once you have set up a CI/CD system, you can configure or add new pipelines (referred to as “Jobs in AIO), edit the system name, view error logs, and delete systems.
To Configure/Add New Job, click on the Pipeline icon (Blue Arrow).
To Edit CI/CD System Details, click on the Edit icon (Green Arrow).
To View Job Logs, click on the Logs icon (Orange Arrow).
To Delete a CI/CD System, click on the Trash Bin icon (Red Arrow).
Steps to Configure a Pipeline
Step 1: To configure a pipeline, click on the Pipeline icon for the desired CI/CD system.
Step 2: Click on the Configure New Job button.
Step 3: Enter the Name of Automation job and the Repository Name into their respective fields and select the Branch from the drop-down list.
If the selected pipeline includes parameters, you can define them in the Inputs and Variables sections.
Users need to enter the Name exactly as it appears in the GitLab pipeline.
Authentication Options
Job Executor Credentials: Whoever is triggering the job, they can use their credentials irrespective of who has created the job.
User Credentials: A specific user can share his/her credential and only that can be used to trigger the jobs. Users setting up the job or editing the job can basically share their credentials for execution with the team.
Custom credentials: Any automation user from the team can use their credentials. It can be used for all the jobs. This can be helpful if the team uses a shared automation user.Trigger Token: A trigger token configured for the selected project can be used to execute the job.
Step 4: Finally, click on the Save button.
Steps to Trigger a Job
Step 1: To trigger a job, simply click on the Pipeline icon.
Once a job is set up, it can be triggered from either the Cycle View or the Cycle Listing View.
Step 2: Click on the Trigger Automation Job button.
Step 3: Finally, click on the Trigger button.
Troubleshooting CI/CD Integration Issues
Trigger token not working during setup?
Trigger tokens are supported only while triggering jobs. Setting up the integration requires a Personal Access Token (PAT).
Why is the connection check succeeding but pipelines are still not working?
During connection validation, the PAT token is checked only for validity and required scopes.
Unable to find branches?
Possible reasons could be:
Invalid Namespace
Invalid Repository Name
Invalid PAT token (does not have access to the repository)
Token expiry
Using sub-groups in GitLab?
Sub-groups are not currently natively supported. As a workaround, users can pass the full path (parent group + sub-group) URL-encoded in the Owner/Organization field.
Example:
If AIO is the parent group and Automation is the sub-group, enter: AIO%2FAutomation
For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.