Introduce continuous integration workflow with ios build as a step

etabakov commented 10 months ago

@vakrilov wondering whether it's worth having this run at push and pull_request or that's an overkill? WDYT?

vakrilov commented 10 months ago

I'm guessing we'd want to fit in the free plan for now. Which is 2000 / 10 (macOS multiplier) = 200 minutes. The build times so far are between 5 and 10 mins, so this makes around 20-40 builds a month, which is not much.

If the only purpose of this actions is "let's see if it builds" - maybe lets only run it for android where it is cheaper.

Ultimately, I think we can need 2 kinds of actions:

[CI] Run tests (when we have such). Maybe it's better to start with android as we should be able to use linux which is x10 cheaper
Build packages needed for publishing to the stores. I think it best to trigger when release is created. We will need macOS there to build for AppStore ;)

etabakov commented 10 months ago

There are cases, especially when updating tooling when one of the native builds will succeed and the other won't. That's why I was thinking we can build both apps. However, we definitely want to stay in the free plan. Maybe run the iOS more rarely somehow?

etabakov commented 10 months ago

Turned out GitHub actions is free for public repos, so merging as is. Thanks GitHub!

5kmrun-bg / fivekmrun-app

Introduce continuous integration workflow with ios build as a step #99