GitLab Connector

by | Apr 2, 2022 | article

Available for

    Ultimate and Enterprise editions

    Get in touch with Sales for licensing questions.

GitLab connector allows the downloading of source files and uploading of target files directly to/from the GitLab repository. The connector uses the GitLab API to implement the integration and allows access to all repositories associated with a GitLab account.

 

Use Cases

There are a number of use cases for the connector:

  • Project Managers can add files directly to projects from an online repository.

  • Set up the Automation Widget to allow Submitters to add files to requests directly from the online repository.

  • Use Automated Project Creation (APC) to have inwhatlanguage automatically create new projects when a change in file size is detected in monitored files or a folder.

    • Due to limitations in the GitLab API, monitoring an entire folder is not supported.

    • Selected documents are imported the very first time APC runs.

    • Use the Git connector if you need to monitor an entire subdirectory.

    • This connector supports absolute path setting. Target translation files can be stored only in the same branch as the source file.

  • Set up Continuous Jobs to have Inwhatlanguage monitor selected files for changes.
  • The Connector API can be used to automate steps otherwise performed manually through the UI. Webhooks can be used to have Inwhatlanguage notify 3rd party systems about certain events (for example, a job status change).

    Tip

    If requirements are:

    • Limiting inwhatlanguage access to a single repository.

    • Using an SSH key for authentication.

    • Monitoring an entire subdirectory for a change in Automated Project Creation.

    • Detection of file changes based on Last modified date as opposed to just file size.

    Use Git connector to connect to GitLab.

    GitLab Settings

    Create an access token in the GitLab account.

    1. Log in to the GitLab account, navigate to Settings and click on Access Tokens.

      The Personal Access Tokens screen opens.

    2. Fill in the Name and Expires at fields. Choose a longer time period so the token doesn’t require frequent recreation.

    3. Under Scopes, check the api and read_user checkboxes.

    4. Click on Create personal access token.

      This generates a token needed to enter into the inwhatlanguage connector configuration.

      • The token is only visible at this stage and cannot be reached afterward.