GitLab version tags
Tell Coralogix when a new build ships, straight from your GitLab deployment pipeline. A pipeline webhook creates a version tag, which is what version benchmark reports compare behavior across.
What you need
- Access to your GitLab project's settings.
- A personal or team API key with the
CICDIntegrationpreset. Presets pick up new permissions automatically; individual permissions have to be maintained by hand. - The GitLab version tags endpoint for your Coralogix domain. Use the domain selector at the top of this page to resolve it: https://api./api/v1/external/gitlab
| Preset | Actions | Grants |
|---|---|---|
| CICDIntegration | VERSION-BENCHMARK-TAGS:READ VERSION-BENCHMARKS-REPORTS:READ VERSION-BENCHMARK-TAGS:UPDATE | View version benchmark tags View version benchmark reports Modify version benchmark tags |
Add the webhook in GitLab
1.
Open the webhook settings
Sign in to GitLab, open your project, then select Settings, then Webhooks.
2.
Enter the URL
Build the URL from the GitLab endpoint for your domain and the query parameters below.
https://api.eu2.coralogix.com/api/v1/external/gitlab?application=APPLICATION_NAME&subsystem=SUBSYSTEM_NAME&name=TAG_NAME
| Parameter | What to enter |
|---|---|
application | Application name as it appears in your Coralogix UI |
subsystem | Subsystem name as it appears in your Coralogix UI. Separate multiple names with commas |
name | The tag name. Omit it and Coralogix derives one from the GitLab payload's project.name and object_attributes.ref fields. See pipeline events |
3.
Add the secret token
Enter your API key in Secret Token, below the URL. This field is required. GitLab sends it in the X-Gitlab-Token header, and Coralogix rejects requests without it.
4.
Trigger on pipeline events
Under Trigger, select Pipeline events, then select Save changes.
Shows the trigger that fires a version tag each time a pipeline's status changes.
Related resources
Last updated on
