Often we may want to receive

[rakibhasanbd4723]

Common parts
At Droids On Roids, we use Slack to communicate within the company. So it may be useful to receive notifications related to Bitrise also there. Usually, each project has dedicated channel for alerts (coming not only from Bitrise). Notification sending is a common action for all the workflows. We can configure it once in utility workflow and then include the latter in regular workflows.

notifications only if something goes wrong. Namely for failed builds, avoiding messages related to successful ones. Such configuration is possible on Bitrise but cannot be configured bulgaria mobile number using graphical WYSIWYG editor. We need to add run_if: ".IsBuildFailed" to step configuration in bitrise.yml mode. Utility workflow looks like that in workflow editor:
Send notification utility workflow

Wrap up
Bitrise workflows can be flexibly configured which gives myriads of possible combinations. Apart from workflows content (steps), we can also configure their triggers. In our app verification workflow is triggered by Pull Requests, staging deployment by merges to the master branch and production deployment by tag pushes. Those (especially deployments) are only examples and may vary in different projects.

You can find the complete configuration of all the workflows below. Note that inputs like API keys, tokens, etc. are saved as secrets so their values are not available.