Merge Request Check Application for Gitlab

Modified on Wed, 26 Mar at 4:26 AM

This help article will guide you through installing and configuring the Merge Request Check application, developed by Cubyts for GitLab. This tool is designed to assist Engineering Leads in gaining a comprehensive view of technology drifts introduced by a Merge Request (MR). By analyzing the changes in a Merge request commit, it helps leads make well-informed decisions on whether to merge the Merge request with the target branch.

Installation and Configuration of the Merge Request Check application

1. Open the URL: https://gitlab.com/explore/catalog/cubyts/technology-drifts; this is the link to the Cubyts CI/CD component that must be integrated with the CI/CD pipeline of a repository to activate the merge check).

2. Check the instructions in the readme file (click on the Readme tab) to deploy the component (note that it's a standard set of steps to be followed to install any CI/CD component in a repository pipeline).

3. The application is now available for use by engineering leads to check technology drifts in all the merge requests belonging to the configured repository.

Note: You must configure the CI/CD component in all the repositories that are connected in Cubyts to ensure that the merge check application is available in those repositories.

Additional steps for Self-hosted Gitlab

Please refer to this article to perform the additional steps required for Gitlab, self-hosted set-up.