Summary - CI/CD

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.

Exercise 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.

Show example solution

{
  "build": {
    "production": {
      "autoIncrement": true
    }
  },
  "submit": {
    "production": {}
  }
}

Exercise 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.

Show example solution

name: CI
on:
  push:
    branches: [main]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: eas build --platform android

Test yourself

What is the first step in the pipeline?
```
git push origin main
```
- It is sent to the store
- Code is pushed
- OTA is published
- The version is bumped
Show answer

Code is pushed — When code is pushed CI triggers.
Match each stage to its role

GitHub Actions

Triggers CI
EAS Build

Compiles in cloud
EAS Submit

Sends to store
OTA

Updates JS

Next lesson: Project design

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies