Trigger a workflow to run in a different stack than the workflow that triggered it

Feature Requests Released
1

Description of the feature request

in the after_run section we can trigger a different workflow. As far as I can tell it isn’t possible to make this other workflow run in a different stack (i.e. different version of Xcode) from the original workflow

Use case / for what or how I would use it

As of Xcode 12.5, module stability for binary frameworks seems to no longer be backwards compatible. This basically means that framework developers who release their frameworks in binary formats need to be building their framework in the oldest version of Xcode supported by the AppStore (12.0 at the time of writing this). However we also need to ensure that it also works in the latest version of Xcode (module stability).

We’ve written a workflow that builds the .xcframework in Xcode 12.0 and publishes it to s3. Then we’ve written another workflow that consumes that .xcframework in Xcode 12.5. Is it possible to trigger the second one from the first one? Or is this a feature that doesn’t exist yet in Bitrise?

The only work around I can see so far is to just have the builds on a schedule, timed an hour apart.

2

Hi, sorry for the unnecessary feature request. I think I’ve figured out a reasonable solution (although there may still be an easier way to do it). I’m now using the Bitrise REST api to trigger the second workflow. This seems to work fine. I can just pass in the additional information through environment variables.

Thanks for looking this over anyway!

3

Thanks for the update! Glad you were able to find a way to do this