Trigger Pipeline with YAML

YAML parameters for Trigger Pipeline

Name Type Description
action Required String The ID of the action.
type Required String The type of the action. Should be set to RUN_NEXT_PIPELINE.
project Required String The name of the project containing the pipeline that will be triggered. Supports environment variables.
pipeline Required String The identifier of the pipeline that will be triggered. Supports environment variables.
comment String The execution comment of the triggered pipeline.
revision String Can be one of HEAD, INHERITor SPECIFIC. Default is HEAD.
specific_revision String Set if you want to run the pipeline for a specific revision or ref.
clear_cache Boolean Set to true if you want the execution to run with the clear_cache flag. Default is false.
refresh Boolean Set to true if you want the execution to run from scratch. Default is false.
environment String The ID of the environment.
priority ExecutionPriority Set if you want the execution to run with priority other than set in the next pipeline. Can be one of LOW, NORMAL or HIGH.
wait Boolean Set to true to wait for the triggered pipeline execution to complete before proceeding. Default is false.
package String The package context identifier for the pipeline execution.

YAML example for Trigger Pipeline

yaml
actions: - action: "Run backend/dev" type: "RUN_NEXT_PIPELINE" comment: "Triggered by $BUDDY_PIPELINE_NAME execution #$BUDDY_RUN_ID" revision: "SPECIFIC" specific_revision: "$BUDDY_RUN_REF" project: "backend" pipeline: "dev" clear_cache: true refresh: true environment: "MY_ENVIRONMENT" priority: "HIGH" variables: - key: "version" value: "$BUDDY_RUN_ID" encrypted: false

YAML example for Trigger Pipeline with dynamic project and pipeline

yaml
actions: - action: "Run check-user-in-es/backup" type: "RUN_NEXT_PIPELINE" comment: "Triggered by $BUDDY_PIPELINE_NAME execution #$BUDDY_RUN_ID" wait: true clear_cache: true refresh: true environment: $env_id priority: NORMAL package: "mypackage:1.1" project: $project pipeline: $project_pipeline

Last modified on Feb 25, 2026