Unfortunately, it can happen that your build triggers do not trigger a build automatically on Bitrise. There are many potential issues that can stop your builds - let’s take a look!
Check your webhooks.
Check that you have the webhook set up correctly. You can find out the webhook URL for your repository’s hosting provider on the
Codetab of your app and you can check in your repository’s settings if they match.
Also, you have to enable the specific event that you would like to trigger a build. For example, if your repository is hosted at GitLab and you wish to trigger builds with Git Tags, you must enable Tag Push events in your GitLab webhook.
Check in your repository’s settings if there are any error messages regarding the delivery attempts related to your webhook.
For more information about potential issues with webhooks, check out Webhook troubleshooting
Check the branch names and tags you set up with the trigger on bitrise.io.
For example, if you accidentally typed
master, no build will be triggered.
Check if you previously enabled Selective Builds for the app. You can find the option on your app’s
Settingspage. With this feature, you can set that a build should be triggered only if certain files or folders have been changed.
Check the status page of your repository’s hosting provider to see if there are any known issues.
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.
Build logs allow users to analyze their builds and find out what went wrong - and what went right! On Bitrise, build logs are easily accessible: they can be viewed...