[jl-gitlab]

Hey, CI/CD PM here. I'd love to learn more about how you're using GitLab for mobile, if you're up for it ping me at @jlenny on gitlab.com. It's an area of focus for us, and it's always great to get to know another person who is using that use case.

[harrisonjackson]

We use it with Fastlane to automate our entire build and delivery pipeline. We set it up for our mobile clients, too, and it saves us a lot of time getting code shipped quickly.

We have a Mojave VM configured with Xcode, Fastlane, and the gitlab runner.

We automate uploads to Appetize.io for every feature branch so that QA and clients can test out new features in a simulator running in the browser.

We automate builds and uploads to Apple test flight and Google playstore alpha tracks on our develop branch.

The gitlab runner is by far the most reliable and easiest to setup part of the whole deal with the worst being maybe cocoapods or npm for the projects that rely on them (react-native).

I'll ping you on gitlab. Happy to go into more detail!

[orf]

> react-native

We've recently run into an issue with building react-native on Gitlab-CI, where apparently the build process spins up a file watcher in the background which quickly exhausts the open file descriptors.

Have you experienced anything like this? We are using stock react-native and not customizing anything.

[harrisonjackson]

Haven't had this issue, no. Are you running into the same problem if you build the app without the runner? The file watcher (do you mean metro?) shouldn't be running during a production build since the files aren't changing, right?