Ketryx Documentation
Book a DemoFAQTraining Videos
  • Introduction
  • 📄Manuals
    • MAN-01 Ketryx Lifecycle Management
    • MAN-02 Software Release Process
    • MAN-03 Supply Chain Management: Software Dependencies
      • Threat Modeling
      • Vulnerability Management
      • Working with CycloneDX
      • Working with SPDX
    • MAN-04 Supply Chain Management: Cloud Dependencies
    • MAN-05 Milestones
    • MAN-06 Test Management
    • MAN-07 Traceability
    • MAN-08 Risk Management
    • MAN-09 Git-Based Configuration Items
    • MAN-10 Managing items in Ketryx
    • MAN-11 Approval Rules
    • MAN-12 Computational Controls
    • MAN-13 Data Export
  • 🛠️Work Instructions
    • WI-01 Requirement
    • WI-02 Software Item Specification
    • WI-03 Task
    • WI-04 Test Case
    • WI-05 Test Execution
    • WI-06 Anomaly
    • WI-07 Complaint
    • WI-08 Change Request
    • WI-09 Corrective and Preventive Action (CAPA)
    • WI-10 Risk
    • WI-11 Document
  • 🌐Integrations
    • Jira
    • Azure DevOps
    • TestRail
    • Jama
    • Polarion
    • Chrome extension
    • Source Code
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Code Change Reviews
    • Release documents
      • Google Workspace
    • Authentication
  • 📚Reference
    • Ketryx Query Language
    • Advanced Settings
    • Glob Pattern Matching Algorithm
    • Traceability Configuration
    • Document Templating
    • Project Settings
    • Custom Item Types
    • Assistant
    • Agents
    • Release Notes
  • 🔃API
    • Authentication
    • Build API
    • Project API
    • Item API
    • Webhooks
Powered by GitBook

Ketryx

  • ketryx.com
  • What is Ketryx?

Resources

  • FAQ
  • Training Videos

© 2025 Ketryx Corporation

On this page
  • 1. Introduction
  • 1.2. Tools
  • 2. Repository access
  • 2.1. Public Repositories
  • 2.2. Private Repositories
  • 3. Access tokens
  • 3.1. Creating a Personal Access Token for GitLab
  • 3.2. Creating a Project Access Token for GitLab
  • 4. Related features
  • 4.1. Using the Code Change Review feature with GitLab

Was this helpful?

Export as PDF
  1. Integrations
  2. Source Code

GitLab

Guide on integrating GitLab with Ketryx

PreviousGitHubNextCode Change Reviews

Last updated 17 days ago

Was this helpful?

1. Introduction

This section provides an introduction to the integration of GitLab with Ketryx. Our focus is on outlining the process of setting up this integration, utilizing Personal Access Tokens and Project Access Tokens, to enhance your software development practices. This guide will walk you through the steps required to establish a connection between GitLab and Ketryx.

1.2. Tools

Tools used to develop and release a product with Ketryx Lifecycle Management are provided in . The release process is described in detail in , while setting up code repositories is described in .

Ketryx does not support Code Change Reviews with GitLab at this time. We are working on adding this feature in the future. Please if you this feature is a priority for you.

2. Repository access

The integration process with GitLab varies slightly depending on whether you are working with public or private repositories. Here's a breakdown of the key differences:

2.1. Public Repositories

  • Accessibility: Public repositories are open to the public, meaning that anyone can view the repository content and its history.

  • Integration Setup: For public repositories, the setup process for integrating with Ketryx is generally straightforward. You do not need to use an access token for basic integration tasks, such as SOUP dependency analysis.

2.2. Private Repositories

  • Accessibility: Private repositories restrict access to authorized individuals or collaborators. Only those with permission can view and interact with the repository.

  • Integration Setup: When integrating with private repositories, you typically require an access token. This token ensures secure and authorized communication between GitLab and Ketryx for tasks like SOUP dependency analysis.

It's important to consider your repository's visibility when setting up the integration, as public and private repositories have distinct access requirements. The integration guide provides specific instructions based on the type of repository you are working with, ensuring a seamless and secure integration experience.

3. Access tokens

3.1. Creating a Personal Access Token for GitLab

3.2. Creating a Project Access Token for GitLab

4. Related features

4.1. Using the Code Change Review feature with GitLab

Please see . The scope read_repository scope should be selected.

An alternative to the Personal Access Token is the Project Access Token. Steps on how to create one can be found in . For the scope, read_repository scope should be selected. For the role of the token, Reporter should be selected.

Ketryx does not support Code Change Reviews with GitLab at this time. We are working on adding this feature in the future. Please if you this feature is a priority for you.

🌐
MAN-01 Ketryx Lifecycle Management
MAN-02 Software Release Process
MAN-03 Supply Chain Management
reach out
GitLab's documentation
GitLab's documentation
reach out