This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# This is a sample build configuration for JavaScript. | |
# Check our guides at https://confluence.atlassian.com/x/14UWN for more examples. | |
# Only use spaces to indent your .yml configuration. | |
# ----- | |
# You can specify a custom docker image from Docker Hub as your build environment. | |
image: node:13.0.0 | |
definitions: | |
caches: | |
npm: ~/.npm | |
jest: .jest | |
pipelines: | |
branches: | |
master: # Ce script s'execute juste quand on push sur la branche master | |
- step: | |
name: Deploy to Expo Production # https://exp.host/@USERNAME/PROJECT?release-channel=CHANNEL | |
deployment: production # used in the Deployments dashboard. Valid values are: test, staging, or production. | |
caches: | |
- npm # keep the npm cache around to speed up installs | |
script: | |
# Modify the commands below to build your Expo project | |
- unset NPM_CONFIG_USER # see: https://github.com/expo/sentry-expo/pull/26#issuecomment-453822980 | |
- npm ci # ci = clean install | |
- npm i -g --unsafe-perm expo-cli # install Expo globally cz npx wasn't working | |
- expo login -u ${EXPO_USERNAME} -p ${EXPO_PASSWORD} # Use variables defined in Repository Settings | |
- expo publish --non-interactive --clear --release-channel production | |
develop: # Ce script s'execute juste quand on push sur la branche develop | |
- step: | |
name: Deploy to Expo Staging | |
deployment: staging | |
caches: | |
- npm | |
script: | |
- unset NPM_CONFIG_USER | |
- npm ci | |
- npm i -g --unsafe-perm expo-cli | |
- expo login -u ${EXPO_USERNAME} -p ${EXPO_PASSWORD} | |
- expo publish --non-interactive --clear --release-channel staging | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment