Manual trigger

View as Markdown

Triggering a pipeline manually lets you specify:

  • The revision, branch or tag for which the pipeline will run
  • The actions to run (for example, if you want to re-deploy the same build)
  • Whether the deployments should be based on the changeset or made from scratch
  • Whether the cache should be cleared before execution
  • The priority of the execution

Image loading...Pipeline with Manual Trigger

Info
Manual triggers work in combination with pipeline contexts. The pipeline will only run if the specified branch/tag matches the configured contexts.

Example

Manual deployment pipeline

This example shows a manual pipeline that builds a Node.js application and deploys it to a production server via FTP, with Slack notifications.

yaml
- pipeline: Deploy App
  refs:
  - :default
  fail_on_prepare_env_warning: true
  variables:
  - key: pipeline_variable
    value: value
    type: VAR
  actions:
  - action: "Build App"
    type: BUILD
    working_directory: /buddy/git-repo
    docker_image_name: library/node
    docker_image_tag: 22
    commands:
    - npm install
    - npm run build
    shell: BASH
  - action: Transfer files
    type: TRANSFER
    targets:
    - my_server
  - action: Send notification
    type: SLACK
    content: "[#$BUDDY_RUN_ID] $BUDDY_PIPELINE_NAME execution by <$BUDDY_TRIGGERING_ACTOR_URL|$BUDDY_TRIGGERING_ACTOR>."
    channel: deploy-status
    integration: your_slack_integration

Last modified on Sep 17, 2026