Skip to main content
All CollectionsRequirements ManagementExternal Sources
Integration with Gitlab self-managed instance as source of requirements
Integration with Gitlab self-managed instance as source of requirements

Hosting Gitlab on premise or at a location other than Gitlab's cloud then read on to know how to integrate it as requirements source

Vishal Vaswani avatar
Written by Vishal Vaswani
Updated over a week ago

This article discusses the process of using Gitlab self-managed instance as a source of requirements, to link Gitlab issues as requirements with test cases in TestCollab. To know about integration with Gitlab SaaS please refer this article.

In order to use the feature you would be adding a new application on your Gitlab instance to allow access to TestCollab.

Adding an application on Gitlab

For this the access to admin area would be required, in admin area:

Adding an application on self-managed Gitlab instance
  • On submitting the form, user will be redirected to application details page

  • Copy the values for Application ID and Secret as they will be required during configuration in TestCollab

Connecting with Gitlab self-managed instance in TestCollab

You must have an administrator's privileges to perform these:

  • Open the project that needs to be configured to use Gitlab self-managed instance

  • Navigate to Settings > Requirements

  • Enable Requirements Management feature

  • Select Gitlab as source of requirements

  • Check "Enable this to enter self hosted instance details".

  • Provide the values for Application ID and Secret that we copied from the new application created in Gitlab

  • Instance URL should be the one you use to access your Gitlab self-managed instance

The next steps, right from signing-in to Gitlab, to configuring the settings and to linking issues from Gitlab as requirements are identical to the ones we follow while integrating Gitlab SaaS

Did this answer your question?