ChangelogDocsPricingContact
Sign inInstall Self-Hosted
Get Started on Cloud
AboutX (Twitter)support@buddy.works
BasicsPipelinesActions & ServicesEnvironmentsIntegrationsTargetsTestsDomainsSandboxesSelf-HostedAgents & TunnelsYAMLBuddy GitFAQAPI
  • Pipelines
  • Introduction
Pipelines
Introduction
New pipeline
Creating a pipeline
Workflow Configuration
YAML templates
Triggering pipelines
On git event
Webhook Trigger
Manual trigger
On schedule
Wildcards
Trigger pipeline action
Advanced trigger types
REST API
Commit commands
Slack slash commands
Contexts
Pipeline loop
Pipeline list
Pipeline filesystem
Pipeline history
Analytics
Advanced settings
Cache
Filesystem cache
Build action cache
Docker cache
Cache maintenance
Builds & testing
Concurrency & parallelism
Conditional runs
DB migrations & custom scripts
Variables
Scope and configuration
Combining phrases
Passing variables
Parameterized pipelines
Passing parameters on run
Passing parameters between pipelines
Manual approval
Folders
SSH keys
Status badges
Private dependencies
Private dependencies
Submodules
Deployment
Node.js packages
Composer PHP packages
Copy pipeline
Duplicating
Export / Import
Pipeline examples
CDN invalidation
Continuous Delivery
Continuous Deployment
Daily integration tests
Deployment pipeline
Link validation pipeline
Monitoring pipeline
Pull requests testing
Release after every tag push
Run tests after every push
Selenium tests
Semantic versioning and settable variables
Zero-downtime deployment
  • Pipelines
  • Introduction

Triggering pipelines

Explore all pipeline trigger types in Buddy, including manual, Git-based, scheduled, pattern-based, webhooks, API, and cross-pipeline triggers.

  • On git event

    Event triggers allow you to automate pipelines making them run whenever specific changes to repository are made

  • Webhook Trigger

    Webhook trigger enables external systems to automatically start pipeline runs via HTTP requests, providing seamless integration with third-party tools and services.

  • Manual trigger

    For production pipelines, it is best to set them to manual mode and restrict access rights to senior devs only.

  • On schedule

    You can set your pipeline to be triggered at a certain time of the day or to run in specific intervals

  • Wildcards

    You can use a pattern to define which branches or tags will trigger the pipeline. The patterns support ref names and ref paths.

  • Trigger pipeline action

    Trigger pipeline lets you create advanced workflows, where several pipelines interact with each other across the whole workspace.

Resources

  • Docs
  • API
  • Terraform
  • Guides
  • Download Self-Hosted
  • Security
  • Blog
  • Tutorials

Company

  • About
  • Customers
  • Support
  • X (Twitter)
  • Responsible Disclosure
  • GDPR
  • Terms of Service
  • Privacy Policy
SOC2
SOC2

© 2026

All systems are operational