A little bit of context (skippable)
These past weeks I've been struggling trying to set up a pipeline where for every PR pointing to our...
For further actions, you may consider blocking this person and/or reporting abuse
When you chose the macos executor instead of the linux_android for the android e2e tests: "Note that all of this can be achieved using the rn/linux_android executor." was there any reason for that choice? The macos minutes are more expensive AFAIK, and you chose to mention both would work, so just curious if it was more difficult to do or something?
p.s. I found that the
rn/ios_build_and_test
command worked just fine when used like this:Currently trying to decide how I can most efficiently configure the e2e tests on release, and ideally use the same build artifacts from that to release through fastlane or something
In the beginning, I tried with the linux_executor. I don't remember exactly why I changed, I think it was related to all the detox dependencies and setting up the environment. (But later other issues came up, so I had to do all of that... At this point, it should be that hard to change the executor, but idk since I need to try it again).
Thanks for the suggestion! I'll make an update with your suggestion with
iOS
.That definitely would save some time. I'm not sure of the implications of publishing the detox build for android. But It would definitely help for ios.
@ Kieran Osgood - Were you able to find a way to reduce the ios build time for detox, using macos or linux as env?
Yeah.... Mayor update, you can get the same result with:
I'll make sure to update this post when I get some time ToT
Thanks for the great article! Do you have any experience in GitHub actions? I tried it before and not works as well as CircleCI.
Sadly I have just use github actions to test detox, but I'm planning on doing this workflow sooner than later for this app in github actions. github.com/Kyonru/just-a-review-app
Thanks! I think maybe there is a problem running iOS build on GitHub actions, whereas CircleCI works much better thanks to the ORB. Looking forward to the GitHub Actions version!
sounds good to automate some react-native dev-ops things, also reading the documentation from react-native-circleci-orb really makes sure you know how hard is what you're about to do.
Thanks for the post, very well detailed.
Could i ask what was the build time for this rn/ios_build step? And if you have thought of ways to reduce it?