Connectors

GitLab Connector

Available in: Ultimate and Enterprise editions
Available for an additional cost in: Team edition

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.

GitLab Connector 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 allowing Submitters to add files to requests directly from the online repository.
  • Use Automated Project Creation to have Memsource automatically create new projects when a change in file size is detected for monitored files.
    • Due to limitations in GitHub API monitoring an entire folder is not supported.
    • Selected files 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. Note that the target translation files can be stored only in the same branch as the source file.
  • Set up Continous Jobs to have Memsource 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 Memsource notify 3rd party systems about certain events (for example, a job status change).

Use Git connector to connect to GitLab if:

  • Limiting Memsource access to a single repository is required.
  • Using an SSH key for authentication.
  • Monitoring a directory for a change in Automated Project Creation is required.
  • Detection of file changes based on Last modified date as opposed to just file size is required.

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 Memsource connector configuration.

    Important:

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

Memsource Settings:

Note:

In some browsers, pop-ups must be enabled in the browser in order to connect.
  1. From the Setup page, scroll down to the Integrations section. Click on Connectors.
    The Connectors page opens.
  2. Click New
    The Create Connector page opens.
  3. Provide a name for the connection and change the Type to GitLab.
  4. Enter GitLab site URL (e.g https://gitlab.com/) and the GitLab personal access token you have obtained from the GitLab site.

    Note:

    In order for Memsource Cloud to access the repository, it must be accessible from the Internet.
  5. Click Test Connections.
    A checkmark will appear if the connection was successful. A red exclamation point will appear if it wasn't. Mouse over the icon to see additional details.
  6. Click Save.
    The connector is added to the list on the Connectors page.

If a default project, branch, and folder is required when connecting to a GitLab account, open the connector configuration and click the Select Remote Folder button to set it.