Skip to main content

GitLab CI (Pipeline Triggers)

The GitLab CI trigger triggers GitLab CI/CD pipelines with custom variables when new container versions are detected, automating automated testing, deployments, or GitOps pipelines.


⚙️ Configuration Variables

WUD_TRIGGER_GITLABCI_{trigger_name}_PROJECTID
Requiredstring

GitLab project ID (numeric ID, or URL-encoded path like mygroup%2Fmyproject)

WUD_TRIGGER_GITLABCI_{trigger_name}_TOKEN
Requiredstring

GitLab Pipeline Trigger Token (generated in Project > Settings > CI/CD > Pipeline triggers)

WUD_TRIGGER_GITLABCI_{trigger_name}_DISABLETITLE
Optionalbooleandefault: false

Whether to omit the notification title in pipeline variables

WUD_TRIGGER_GITLABCI_{trigger_name}_REF
Optionalstringdefault: main

Git branch or tag name to run the pipeline on

WUD_TRIGGER_GITLABCI_{trigger_name}_URL
Optionalurldefault: https://gitlab.com

GitLab instance base URL (can be customized for self-hosted GitLab instances)

info

This trigger also supports all common trigger configuration options (such as thresholds, scheduling, and batching).


📦 Injected Pipeline Variables

When the pipeline is triggered, WUD supplies the following environment variables:

VariableDescription
WUD_MODETrigger execution mode (simple or batch)
WUD_CONTAINERName of the updated container
WUD_WATCHERName of the watcher that detected the container
WUD_IMAGEBase container image name
WUD_LOCAL_TAGCurrently running container tag
WUD_REMOTE_TAGNewly available remote image tag
WUD_LINKRegistry or release notes link
WUD_TITLEFormatted update title
WUD_MESSAGEFormatted update message body

🚀 Examples

Basic Pipeline Trigger

services:
whatsupdocker:
image: getwud/wud
environment:
- WUD_TRIGGER_GITLABCI_DEPLOY_PROJECTID=12345678
- WUD_TRIGGER_GITLABCI_DEPLOY_TOKEN=glptt-secrettrigger123456
- WUD_TRIGGER_GITLABCI_DEPLOY_REF=main