Summary - CI/CD
- React Native course
- Advanced
- Lesson 78/83
- 5 min
Combine EAS Build, eas.json and OTA updates to write a release pipeline.
Summary - CI/CD
In this group you saw EAS Build, EAS Submit, eas.json, GitHub Actions and OTA updates. A release pipeline flows like this: code is pushed, GitHub Actions triggers, tests run, EAS Build compiles, EAS Submit sends to the store. JS changes spread instantly via OTA.
In the final lesson you will write an eas.json that combines all pieces. The file will carry both build and submit sections; it will also include a channel profile for OTA. This way one file drives the whole release.
Practice Write a combined eas.json
Write an eas.json. The root object holds a "build" section with a "production" profile carrying "autoIncrement" set to true. Also add a "submit" section with a "production" profile inside.
Starter code
{
// add build and submit sections here
}Sample solution
{
"build": {
"production": {
"autoIncrement": true
}
},
"submit": {
"production": {}
}
}Practice Add a GitHub Actions step
Add an EAS build step to a YAML workflow. Under jobs add a build job with a steps list and a run step that runs eas build --platform android.
Starter code
name: CI
on:
push:
branches: [main]
# add jobs and the eas build step hereSample solution
name: CI
on:
push:
branches: [main]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: eas build --platform androidQuestions and answers
Review the lesson questions together with their answers. To test yourself, solve the lesson interactively.
1 What is the first step in the pipeline?
git push origin main- It is sent to the store
- Code is pushed Correct answer
- OTA is published
- The version is bumped
Explanation: When code is pushed CI triggers.
2 Match each stage to its role
| Term | Meaning |
|---|---|
GitHub Actions |
Triggers CI |
EAS Build |
Compiles in cloud |
EAS Submit |
Sends to store |
OTA |
Updates JS |