Trigger Pipeline with YAML

Tip

Learn more about: - Trigger Pipeline action features - Trigger Pipeline integrations - Trigger Pipeline alternatives

YAML parameters for Trigger Pipeline

Hint

List with common parameters for all Buddy actions

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.
pipeline `Required`	String	The identifier of the pipeline that will be triggered.
comment	String	The execution comment of the triggered pipeline.
revision	String	Can be one of `HEAD`, `INHERIT`or `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"
  project: "backend"
  pipeline: "dev"
  clear_cache: true
  refresh: true
  environment: "MY_ENVIRONMENT"
  priority: "HIGH"
  variables:
  - key: "version"
    value: "$BUDDY_RUN_ID"
    encrypted: false

Last modified on Jul 31, 2025

Transfer Visual tests