Could Someone Give me Advice on Understanding Best Practices for Workflow Triggers?

[roberrttt]

Hello there,

I am new to using Bitrise and am loving how flexible and customizable it is. Although; I have hit a bit of a snag when it comes to setting up workflow triggers. I have read through the documentation; but I still feel like I might be missing some nuances, so I was hoping to get advice from the community here.

My goal is to automatically trigger the appropriate workflows depending on which branch is being pushed to and which platform specific changes are being made.

Avoiding unnecessary builds when there are no changes to platform-specific files. Managing triggers for hotfix branches that occasionally come directly from main. Ensuring I am not overloading the build queue unnecessarily for minor changes.

Also, I have gone through this post; https://discuss.bitrise.io/t/how-to-trigger-multiple-workflows-at-the-same-time-machine-leraning which definitely helped me out a lot.

Are there any best practices or tips you could share to optimize this setup? Perhaps there are steps in the workflow I should consider splitting further or a more dynamic way to handle triggers based on file changes?

Thanks in advance for your help and assistance.

[kaushal.bitrise]

Hi @roberrttt

Thanks for the message and welcome to Bitrise. You might have seen the link to our documentation on triggers, but sharing it here nevertheless - Build triggers - Bitrise Docs

To set up an automatic trigger for a workflow on pushes to a branch, you can use the push trigger. Screenshot below:

Based on your earlier post, you can consider setting up two conditions on this trigger:

• Push branch
• File changes

You can add both conditions one after the other on the same trigger.

Let me know how you get along or if you need more help

Thank you.