GitLab Integration

The GitLab Integration is used to connect Shippable DevOps Assembly Lines platform to your instance of GitLab so that you can run builds for your repositories hosted there.

Creating an Integration

You can add this integration by following steps on the Adding an integration page.

Here is the information you need to create this integration:

  • Integration type -- Gitlab
  • Name -- choose a friendly name for the integration
  • URL -- location of your GitLab API. The URL should be in the format https://(GitLab URL)/api/(api version). For example, if you're using gitlab.com, this will be https://gitlab.com/api/v4. Please note that if you're using Gitlab version 9.0 or later, you should use v4 for api version. If you're using Gitlab version 8.17 or earlier, you should use v3 for api version. API v3 is unsupported from Gitlab 9.5 according to this Gitlab notice
  • Token -- GitLab private token with the right levels of permission

Usage in Assembly Lines

The Gitlab integration can be used in the following resources:

Default Environment Variables

When you create a resource with this integration, and use it as an IN or OUT for a runSh or runCI job, a set of environment variables is automatically made available that you can use in your scripts.

<NAME> is the the friendly name of the resource with all letters capitalized and all characters that are not letters, numbers or underscores removed. Any numbers at the beginning of the name are also removed to create a valid variable. For example, my-key-1 will be converted to MYKEY1, and my_key_1 will be converted to MY_KEY_1.

Environment variable Description
<NAME>_INTEGRATION_URL GitLab API location
<NAME>_INTEGRATION_TOKEN The Token used to connect to GitLab

Shippable Utility Functions

The platform also provides a command line utility called shipctl that can be used to retrieve the values of these environment variables.

The specific function that can be used in the jobs yml is: shipctl get_integration_resource_field <resource name> <field name>.

Here is a table that provides the mapping from the environment variable to the field name.

Environment variable Field Name
<NAME>_INTEGRATION_URL url
<NAME>_INTEGRATION_TOKEN token

More information on other utility functions is documented here.

Further Reading