On git event
Event triggers allow you to automate pipelines making them run whenever specific changes to repository are made
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
Webhook Trigger
Webhook trigger enables external systems to automatically start pipeline runs via HTTP requests, providing seamless integration with third-party tools and services.
Email Trigger
Learn how to trigger Buddy pipelines via email with custom parameters, attachments, and security settings. Complete guide to email triggers in CI/CD automation.
Wildcards
You can use a pattern to define which branches or tags will trigger the pipeline. The patterns support ref names and ref paths.
On sandbox event
Sandbox event triggers allow you to automate pipelines based on sandbox lifecycle events: when a sandbox is created, deleted, or timed out.
Trigger pipeline action
Trigger pipeline lets you create advanced workflows, where several pipelines interact with each other across the whole workspace.
On unit test event
Unit test event triggers run a pipeline when a unit test session ends. Filter by branch, test suite, and session status to publish only after tests pass or to react to failures.
On artifact event
Artifact event triggers run a pipeline when an artifact version is created, published, or deleted. Filter by artifact, ID pattern, and scope to react only to the releases you care about.
On environment event
Environment event triggers run a pipeline when an environment is created or deleted. Filter by environment ID pattern, scope, and tags to provision or tear down resources automatically.