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.
next_pipeline_id Required Integer The ID of the pipeline that will be triggered. Not required if both next_project_name and next_pipeline_name are set instead.
next_project_name Required String The name of the project containing the pipeline that will be triggered. Not required if next_pipeline_id is set instead.
next_pipeline_name Required String The name of the pipeline that will be triggered. Not required if next_pipeline_id is set instead.
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.

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" next_project_name: "backend" next_pipeline_name: "dev" clear_cache: true refresh: true environment: "MY_ENVIRONMENT" priority: "HIGH" variables: - key: "version" value: "$BUDDY_RUN_ID" encrypted: false

Last modified on Mar 4, 2025