Hey! :wave: Do you share a repo for all the target...

# multiplatform

[Nacho Ruiz Martin]

Hey! 👋
Do you share a repo for all the targeted platforms?
If so, how’s the recommended CI setup regarding branches to allow independent deployments/releases on each platform?
Thanks!

[Milica Siriški]

I prefer to use one repo for all platforms (so far that's Android and iOS), but I configure separate pipelines for each platform.

Meaning if you were to run build and tests you would have 2 pipelines and if you were to also add release jobs you would have 4. Standard Android and iOS pipelines usually work by just updating the target folder to corresponding subfolder.

[Nacho Ruiz Martin]

Sounds reasonable, thanks.
And how do you trigger those flows? Do you use prefixed tags or something like that?

[Milica Siriški]

That could work, I usually want to run build and test on both and release on schedule so I haven't used anything like that

[leandro]

We use tags with prefixes to trigger releases per platform

[Edoardo Luppi]

We always build everything on each commit. We want to be sure everything is kept in sync and any error surfaces immediately.

[Edoardo Luppi]

But yes, the repo obviously contains all the supported platforms.

Building everything at once ensures the pipeline is as simple as possible, which equals in less maintenance.

[Nacho Ruiz Martin]

Building is OK, but what about publishing or deploying? That can't be done on each commit and, I guess, it's better to do it independently per platform.

[Edoardo Luppi]

Ahh yes, our release process is a bit cumbersome as we have to deal with a lot of security stuff.

The pipeline always archives all the built artifacts, and then an additional pipeline handles releases on demand, but they get pushed simultaneously, all of them.

[Nacho Ruiz Martin]

Oh, OK, that makes sense. Thanks for the info!

[Edoardo Luppi]

Sometimes a platform may just get a version bump, with no changes. It's a trade off and it works OK here

[Nacho Ruiz Martin]

Ok, got it!