digital-blueprint/GitLab Pipeline Trigger

Triggers and waits for a GitLab pipeline to complete

Trust Signals

name	description	required	default
host	The GitLab host to trigger the pipeline.	no	gitlab.com
id	The ID or URL-encoded path of the project owned by the authenticated user.	yes	""
ref	The branch or tag to run the pipeline on.	yes	""
trigger_token	Pipeline Trigger Token, see https://docs.gitlab.com/ee/ci/triggers/index.html#create-a-trigger-token	yes	""
access_token	Pipeline Access Token, see https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html	no	""
variables	A map of key-valued strings containing the pipeline variables. For example: { VAR1: "value1", VAR2: "value2" }.	no	{}
download_artifacts	Whether to download the pipeline artifacts. Requires access_token to be set.	no	false
download_artifacts_on_failure	Whether to download artifacts even when the pipeline fails. Requires access_token and download_artifacts to be set.	no	true
download_job_logs	Whether to download job console output. Requires access_token to be set.	no	false
fail_if_no_artifacts	Whether to fail the action if no artifacts are found. Requires download_artifacts to be enabled.	no	false
download_path	Path where to save downloaded artifacts and logs. Defaults to ./downloads	no	./downloads
verbose	Whether to enable verbose logging. When disabled, only generic messages are shown without sensitive information like URLs, IDs, or names.	no	false

name	description
status	The status of the pipeline.
web_url	The URL of the pipeline.
artifacts_downloaded	Whether artifacts were successfully downloaded.