With only one concurrency available you can just start children builds but without waiting for them. In such case you may need some additional config eg. when using GitHub: additional steps for setting statuses.
Thanks for the answer @koral , but could you give me more details about that? Because I can not:
- Launch multiple workflows with the same trigger, already reported in here. The Bitrise UI doesn’t allow it.
- Make this solution work with just one concurrency plan, without having the first workflow waiting forever for the second one to be executed.
I guess you mean starting a workflow just after other one but what happens if the second one fails? The first one, triggered by a GitHub push for instance, could be successful and it would send a green check to GH when that’s not true. Github webhooks work with Bitrise app tokens, not with Bitrise workflow tokens so I can not distinguish them. About statuses, basically the same, Github detects events from the Bitrise app, not the workflows.
So, what’s the solution? Creating as many apps as modules you want to test with Virtual Device Testing? It would be a mess.