GitLab CI integration

Integrate GitLab CI with OpenText Core Software Delivery Platform, utilizing webhooks and secure credentials.

The integration enables you to receive and process pipeline events from GitLab, providing enhanced visibility and traceability for your CI/CD workflows.

In this topic:

Supported features

The GitLab CI integration provides the following functionality within OpenText Core Software Delivery Platform.

Pipelines and builds

• Collect pipeline step results
• Run pipeline
• Run pipeline with parameters

Hierarchy in topology

• Multi-branch pipeline
• Multiple spaces

Test automation

• Run on-demand automated JUnit tests
• Run UFT One automated tests
• Run Cucumber automated tests

Back to top

Prerequisites

Before starting the integration, ensure you have the following:

• GitLab.com, GitLab dedicated, or self-managed GitLab version 18.8 and above
• Administrator access on space and workspace
• Administrator access to your GitLab projects
• (Optional) Ultimate GitLab license for group/instance-level features

Back to top

Configuration parameters

Configure the following parameters to support the GitLab integration.

For details, see Configuration parameters.

Back to top

Prepare GitLab access tokens

To allow interaction with GitLab, you need an access token. The token must be able to read repository data and variables as needed for your integration scenario. You can create one of the following token types: Personal access token, Project-level token, Group/instance-level token.

Token requirements:

You still need at least Maintainer role to create the webhook manually in the GitLab project.

For details, refer to the GitLab documentation.

Back to top

Set up credentials

Add the GitLab token as credentials in OpenText Core Software Delivery Platform.

To add credentials:

1. Open the global menu and select Administration > General Settings.

2. Select a shared space or workspace.

3. Select the Credentials tab.

4. Click the + Credentials button.

5. Paste the GitLab token into the password field.
6. In the Name and User Name fields, assign descriptive values that help identify the credential, such as the associated GitLab user or purpose.

Back to top

Add a GitLab CI server

CI servers are defined at the workspace level.

To add a GitLab CI server:

1. Select a workspace.
2. Select the DevOps > CI Servers tab.
3. Click the + CI Server button.
4. Enter a name for the CI server and select GitLab as the CI Server Type.
5. Enter the base URL for your GitLab instance. Example: http://example.gitlab.com.
6. After the CI server is created successfully, add the Credential field to the CI server grid and assign the previously created credential.

Back to top

Create API access tokens

Create API access tokens to use in the GitLab wekhooks.

To create API access tokens:

1. Select the shared space .
2. Select the API Access tab.
3. Click the + API access button.
4. Select Token as the type.
5. Assign the CI/CD Integration role for the relevant workspace.
6. Copy the generated token and store it securely. It is displayed only once. If lost, the token needs to be regenerated.

Back to top

Configure GitLab webhooks

Webhooks can be defined at the project or group level (depending on your GitLab license). Go to your GitLab project or group, and add a webhook with the settings below.

Back to top

Work with pipelines

Use the following procedures to work with GitLab pipelines in OpenText Core Software Delivery Platform.

Add a GitLab pipeline

1. Open the global menu and select Quality Management > Pipelines > Management.
2. Click the + Pipeline button.
3. Select the GitLab CI server you configured, then choose the relevant job from your GitLab project.

A multi-branch pipeline is created in OpenText Core Software Delivery Platform, which serves as a reference to the corresponding GitLab project.

Manage multi-branch pipelines

Multi-branch pipelines automatically track runs from any branch in your GitLab project. Users can configure branch filters to control which branches are monitored and injected into OpenText Core Software Delivery Platform.

View pipeline runs and test results

Pipeline runs are displayed in OpenText Core Software Delivery Platform from GitLab. Note the following:

• Configure your YAML file to archive XML test result files at the end of each test job.
• The test results injection process is controlled by CI_INTEGRATION_GITLAB_BDD_CUCUMBER_TESTS_ARTIFACT_NAME and CI_INTEGRATION_GITLAB_JUNIT_TESTS_ARTIFACT_NAME.
• After the job completes, the results are analyzed and displayed in the pipeline run.

The values of CI_INTEGRATION_GITLAB_BDD_CUCUMBER_TESTS_ARTIFACT_NAME and CI_INTEGRATION_GITLAB_JUNIT_TESTS_ARTIFACT_NAME must be different. These parameters are mandatory for test results injection. For UFT One testing, CI_INTEGRATION_GITLAB_JUNIT_TESTS_ARTIFACT_NAME is reused.

The artifact file that contains test result paths must use the following JSON structure:

JSON file structure:

{
    "job_id": 12345,
    "artifacts_base_path": "my-path/test-artifacts",
    "files": [
        { "path": "my-path/test-artifacts/test1.xml" },
        { "path": "my-path/test-artifacts/test2.xml" }
    ]
}

• job_id: The job ID that generated the test result artifacts.
• artifacts_base_path: The common folder path to the test results.
• files: The array that contains test result file paths.
• path: The full path to a test result file, including the file name.

Test results injection may fail if files to download are empty or have an invalid format. Supported formats are JSON (for path/input files) and XML (for test result files). Any other format is rejected.

Back to top

Run pipelines

You can run single-branch pipelines directly from OpenText Core Software Delivery Platform. Multi-branch pipelines can only be run from GitLab.

Set the CI_INTEGRATION_GITLAB_USE_PARAMETERS accordingly to support pipelines with parameters or variables. It is recommended to use input parameters rather than variables.

[
	{
	"{{param_name}}": {{param_value}}
	}
]

Back to top

Run tests

Test runners in OpenText Core Software Delivery Platform enable users to execute automated tests through dedicated GitLab pipelines.

The corresponding pipeline for the test runner needs to be added to OpenText Core Software Delivery Platform prior to running automated tests.

Configure the following variable at the instance, group, or project level in GitLab: testsToRun.

Example (Maven): mvn clean test -DTest=$testsToRun

When creating a test runner in OpenText Core Software Delivery Platform, select the appropriate testing framework (for example, JUnit, UFT, or Cucumber). The testsToRun parameter is generated automatically based on the selection.

Back to top