Learn how to trigger builds on EAS for your app from a CI environment such as GitHub Action and more.
This document outlines how to trigger builds on EAS for your app from a CI environment such as GitHub Actions, Travis CI, and more.
Before building with EAS on CI, we need to install and configure eas-cli. Then, we can trigger new builds with the eas build command.
To trigger EAS builds from a CI environment, we first need to configure our app for EAS Build and successfully run a build from our local machine for each platform that we'd like to support on CI.
If you have run eas build -p [all|ios|android] successfully before, then you can continue.
If you haven't done this yet, see Create your first build guide and return here when you're ready.
Next, we need to ensure that we can authenticate ourselves on CI as the owner of the app. This is possible by storing a personal access token in the EXPO_TOKEN environment variable in the CI settings.
See personal access tokens to learn how to create access tokens.
Now that we're authenticated with Expo CLI, we can create the build step.
To trigger new builds, we will add this script to our configuration:
npx eas-cli build --platform all --non-interactive
This will trigger a new build on EAS and print the URLs for the built files after the build completes.
Add the following code snippet in .travis.yml at the root of your project repository.
---
language: node_js
node_js:
- node
- lts/*
cache:
directories:
- ~/.npm
before_script:
- npm install -g npm@latest
jobs:
include:
- stage: build
node_js: lts/*
script:
- npm ci
- npx eas-cli build --platform all --non-interactive
Add the following code snippet in .gitlab-ci.yml at the root of your project repository.
image: node:alpine
cache:
key: ${CI_COMMIT_REF_SLUG}
paths:
- .npm
# or with yarn:
#- .yarn
stages:
- build
before_script:
- npm ci --cache .npm
# or with yarn:
#- yarn install --cache-folder .yarn
eas-build:
stage: build
script:
- apk add --no-cache bash
- npx eas-cli build --platform all --non-interactive
Add the following code snippet in bitbucket-pipelines.yml at the root of your project repository.
image: node:alpine
definitions:
caches:
npm: ~/.npm
pipelines:
default:
- step:
name: Build app
deployment: test
caches:
- npm
script:
- apk add --no-cache bash
- npm ci
- npx eas-cli build --platform all --non-interactive
Add the following code snippet in circleci/config.yml at the root of your project repository.
version: 2.1
executors:
default:
docker:
- image: cimg/node:lts
working_directory: ~/my-app
jobs:
eas_build:
executor: default
steps:
- checkout
- run:
name: Install dependencies
command: npm ci
- run:
name: Trigger build
command: npx eas-cli build --platform all --non-interactive
workflows:
build_app:
jobs:
- eas_build:
filters:
branches:
only: master
Add the following code snippet in .github/workflows/eas-build.yml at the root of your project repository.
name: EAS Build
on:
workflow_dispatch:
push:
branches:
- main
jobs:
build:
name: Install and build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 18.x
cache: npm
- name: Setup Expo and EAS
uses: expo/expo-github-action@v8
with:
eas-version: latest
token: ${{ secrets.EXPO_TOKEN }}
- name: Install dependencies
run: npm ci
- name: Build on EAS
run: eas build --platform all --non-interactive