Wildcard patterns let you specify which branches or tags will trigger the pipeline execution. This feature is especially useful for testing and deploying multiple branches on development servers.

How to run application tests on push to any branch in the repository

  1. Create a new pipeline
  2. Set the trigger mode to 'On push'
  3. Set the wildcard to *
  4. Add build action for your type of language/framework (eg. PHP)

This way Buddy will automatically test your app on every push, no matter what branch you pushed to.

How to test and deploy all 'dev' branches

  1. Create a new pipeline
  2. Set the trigger mode to 'On Push'
  3. Set the wildcard to dev/*
  4. Add build action for your type of language/framework (eg. Node.js)
  5. Add deployment action for your type of server (eg. SFTP)

This way Buddy will test and deploy your app parameterizing the path according to the deployed branch

Setting up wildcards
Setting up wildcards

Wildcard syntax

In Buddy you can use two kinds of syntax to define wildcard patterns:

SIMPLE

Patterns are created with an asterisk *, for example:

  • * - all branches and tags
  • dev* - all branches starting with dev

REGEX

The whole pattern must be enclosed in brackets, eg:

  • (.*) - all branches and tags
  • (refs/tags/.*) - all tags, no branches
  • (refs/heads/.*) - all branches, not tags
  • (refs/heads/dev.*) - all branches starting with dev
  • (refs/heads/(?!master).*) - all branches except master branch