Mobile Development and doing any kind of Android CI sucks ass 🤦♂️ Been trying all weekend to set-up some CI (self-hosted of course) for Android builds. The fucking goddamn build gets OOM killed at 2GB of memory 🤣 Goddamnit, this whole Mobile space is just utter rubbish 😅
@apex@rawtext.club Ahh thank you so much! 🙇♂️ Just looking to have some simple CI/CD going for the Yarn.social App written in Dart/Flutter.
Of course I’m hell bent on self-hosting the CI infra with Gitea’s nice new sexy Actions support 👌
@apex@rawtext.club Do you also have experience on the iOS side of things? 🤔
@apex@rawtext.club Fair enough 😆
@apex@rawtext.club So can I share my workflow with you and see if there are any memory optimizations that can be had? 🤔
@apex@twtxt.net https://git.mills.io/yarnsocial/app/src/branch/master/.gitea/workflows/build.yml – 1GB of memory, I also tried 2GB and the workflow also failed 😱 I’m limited by hardware at this point, my underlying machines just don’t really have more to spare (32GB ea and they’re all sitting around ~80%+ utilisation)
@apex@twtxt.net Oh nice! How cool 😅 Yeah there has to be some fine-turning we can work out for Android/Gradle builds that don’t consume a tonne of RAM 🤣 Under normal circumstances in Github Actions I’m sure this is fine, 3.8GB, but on your own much more constrained hardware, I’d have to shutdown a tonne of services just to run CI? 😳