Triggering builds with Git Tags

You can specify a pattern for your Git Tags to trigger a specific workflow. This is a good way to build and deploy your app in a specific state. And it’s very easy to set up!

Webhooks for triggering builds

Triggering builds automatically requires an incoming webhook set up with the hosting service of your repository. Read more in the Webhooks section.

Note that certain providers, such as GitLab, require Tag Push events to be specifically enabled in the webhook setup.

Open your app on bitrise.io.
Open the Workflow Editor.
Select the Triggers tab.
Select the TAG option.
Click + ADD TRIGGER.
In the TAG window, add the tag that you wish to trigger a build.
Select the workflow you wish to trigger (for example, primary).
Click Save in the top right corner.

Using patterns when specifying a branch or tag

The * symbol can be used in your configured triggers as a wildcard in branch or tag names. It can also be used in patterns. For example, the pattern *-dev can be used for any branches or tags with the suffix -dev. Please note that when there are multiple triggers, only the first matching trigger will start a workflow.

And you’re done!

You can trigger and abort builds with the Bitrise API. Define parameters for the build: for example, branch, tag or git commit to use. Custom environment variables can be defined...

Both incoming and outgoing webhooks can be set up with the Bitrise API. They are important for automatic build triggering and the reporting of build events to other services.

You can schedule your builds to run automatically at a specific time of the week so that you can check your logs when it's most convenient for you.

Environment Variables (Env Vars) consist of a key and a value, as well as optional attributes. They can be defined on the level of apps, Workflows or Steps.