Fork me on GitHub
#cljsrn
<
2016-07-20
>
vikeri09:07:05

Wrote a blog post on how to quickly get started using Gitlab CI and Docker to test our RN builds: https://pilloxa.gitlab.io/posts/ci-with-gitlab-and-docker/ feedback welcome.

artemyarulin09:07:15

oh cool. So, basically I’ll need to have custom Gitlab installed on OSX if I want to test iOS things?

artemyarulin09:07:51

I’ve been using CircleCI before for that, but went away from it because they don’t have free plan for open source(

vikeri09:07:11

@artemyarulin: You only have to install gitlab-ci-muti-runner not a full Gitlab instance. Actually I’m just doing nodejs tests at the moment. No integration tests with an iOS simulator yet. But yeah that should work in the future as well: https://about.gitlab.com/2016/03/10/setting-up-gitlab-ci-for-ios-projects/

artemyarulin09:07:50

Thank you, it’s nice because I’m using GitHub heavily, don’t want to go from it, thank you @vikeri BTW: CircieCI is actually better now: https://circleci.com/pricing/#build-os-x, just 40$ per month for the smallest plan. Previously it was like 80

artemyarulin09:07:55

with travis you would get unlimited 2 jobs, but with 130$

artemyarulin09:07:38

or you can rent a macOS server and install Jenkins there like in old good times 🙂

vikeri09:07:31

@artemyarulin: Yes, once you need iOS simulators I guess one of those choices are needed. Or I might install the gitlab runner on an old unused Mac in the office. But that seems quite fickle 😜

boorad13:07:03

@vikeri: did you ever get RN updated in boot-react-native example app? https://github.com/mjmeintjes/boot-react-native/issues/49

boorad13:07:28

seems like the bundle is going to the ole ~/Library/Developer/… location but simulator is looking for it in build/Build/Products/Debug-iphonesim...

boorad13:07:31

I’m trying with 0.29.0, and getting dreaded __fbBatchedBridge is undefined

boorad14:07:49

I’m on @pesterhazy ’s develop branch, with only a couple of changes so far… any ideas?

pesterhazy16:07:35

@boorad: I haven't had time lately to work on it

pesterhazy16:07:15

the error you're seeing is just a generic error meaning that the js runtime couldn't find the js, or that there was some sort of early error (syntax errror?)

pesterhazy16:07:35

as for bundle.js, that shouldn't matter in development mode

pesterhazy16:07:50

or I guess main.js normally

pesterhazy16:07:00

that's the so-called "offline bundle", which is only used in release builds

pesterhazy16:07:53

so if you're using "boot dev", that shouldn't matter

pesterhazy16:07:35

I got stuck in the RN update at some point; I think I need to go back and start from a simple js file

pesterhazy16:07:46

but I'm keen to fix this, so let me know if you make any progress

vikeri17:07:51

@pesterhazy and @boorad: still on re-natal since I don't have the boot skills to work it out. Would be stoked to switch though, and willing to help out of someone could point me in the right direction.

boorad19:07:32

okay, so I added back the bit that skips the Sim bundling, as I am doing boot dev -p ios and don’t need it. Then something inside boot-react-native barfs, maybe I’m building in build/Build, but not telling the sim where to load from.

boorad19:07:45

this CFBundleIdentifier error had me changing jsCodeLocation in AppDelegate.m between ‘localhost' and '%@'

boorad19:07:49

now neither work

boorad19:07:27

(and if this is the wrong channel, plz let me know. Thought about #C0N43QHHT)

boorad20:07:21

@pesterhazy: how were you getting that flexible :app-dir into run-in-simulator fun?

boorad20:07:26

nm, found it... -A