ChangelogDocsPricingContact
Sign inInstall Self-Hosted
Get Started on Cloud
AboutX (Twitter)support@buddy.works
BasicsPipelinesActions & ServicesEnvironmentsIntegrationsTargetsDomainsSelf-HostedAgents & TunnelsYAMLBuddy GitTroubleshootingAPI
  • Pipelines
  • Introduction
  • Triggering pipelines
Pipelines
Introduction
New pipeline
Creating a pipelineYAML templates
Triggering pipelines
Basic trigger modes
Manual triggerOn git eventOn scheduleWildcards
Advanced trigger types
WebhooksREST APICommit commandsSlack slash commands
Trigger pipeline action
Pipeline listPipeline historyPipeline filesystemAnalyticsAdvanced settings
Cache
Filesystem cacheBuild action cacheDocker cacheCache maintenance
Builds & testingConcurrency & parallelismConditional runsDB migrations & custom scripts
Variables
Scope and configurationCombining phrasesPassing variables
Parameterized pipelines
Passing parameters on runPassing parameters between pipelinesManual approval
FoldersSSH keysStatus badges
Private dependencies
Private dependenciesSubmodulesDeploymentNode.js packagesComposer PHP packages
Copy pipeline
DuplicatingExport / Import
Pipeline examples
CDN invalidationContinuous DeliveryContinuous DeploymentDaily integration testsDeployment pipelineLink validation pipelineMonitoring pipelinePull requests testingRelease after every tag pushRun tests after every pushSelenium testsSemantic versioning and settable variablesZero-downtime deployment
  • Pipelines
  • Introduction
  • Triggering pipelines

Basic trigger modes

Learn how to trigger pipelines manually, on Git events, on schedule, or using pattern-based rules.

Pipelines in Buddy can be triggered in three different ways:

  • Manually – on click via Buddy's website
  • On event – on git events like push to repository, branch deletion or creation
  • Schedule – on a time interval
  • Manual trigger

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

  • On git event

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

  • 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.

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

© 2025

All systems are operational