IGAPP-665: Disable flipper builds in CI

[maxammann]

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

[sarahsporck]

Saved around 10 mins, as expected. Might be worth it 🤷🏼‍♀️. But only if there actually is an easy workaround.

[maxammann]

Yep, worth it, not sure yet how to handle the lock file.

• One solution would be to have two lockfiles.
• The other is to remove the --deployment as I did for testing

[steffenkleinle]

The option with two lockfiles would provide additional security as it is always clear which dependencies are used, right? Could lead to diverging dependencies though...

[maxammann]

The option with two lockfiles would provide additional security as it is always clear which dependencies are used, right? Could lead to diverging dependencies though...

Actually this is not possible with cocoapods, so this is only a theoretical option :D

[sarahsporck]

Actually why would you want to enable flipper on main? As far as I know flipper is/should also not be linked in release mode. Probably I am missing something, right?

[steffenkleinle]

It is more about enforcing the correct dependencies/lockfile and flipper on main is just a drawback.

[maxammann]

I decided to just remove the --deployment flag, because:

• Conditionally using the flag or not adds a lot of complexity to CI scripts
• The benefit is not clear. 99% of people do not use these flags
• If you forget to update the lock file then somebody will eventually find it or the build will fail in other ways.