CICD for React Native
summary
Sets up a concrete CI/CD recipe for React Native: use CircleCI to run tests and trigger builds, Fastlane (with match) to sign and publish to Play internal test track and TestFlight, use react-native-config and react-native-schemes-manager for three build flavors, store keystore and Google Play JSON in CI variables, auto-increment build numbers from commit count, and add icon badges. Initial setup takes about two weeks, repeat setup drops to two days and automation via react-native-ci cuts deploys to under two minutes.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:16The Dilemma
- 2:21Introducing Juha
- 2:59What was our solution
- 3:58Continuous Integration
- 6:57Build Flavors
- 8:11Cloud Service
- 9:09Benefits
- 10:37Steps
- 11:39Integration
- 12:10Configuration
- 14:15React Native config
- 15:03Sharing secrets
- 18:25Version Numbering
- 19:25Icon Patches
- 20:45Test Track
- 21:43Slack Notification
- 23:02Customer problem
- 24:36Automation
- 25:19Pull Request
- 25:42Fully Automated
- 26:08React Native CI
related talks
27mPractical CI/CD for React Native
24mAutomate your React Native world with fastlane
41mAutomating mobile applications from dev to production
19mWorld Class experience with React Native
31mThe Final Push: Deploying React Native
30mSigned, sealed, deployed: shipping React Native apps
33mFrom development to store with React Native and VSTS
35mWeb-Like Development and Release Agility for React Native