Mobile - Add expo workflow yaml for allowing devs to trigger manual builds #349
There are no files selected for viewing
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 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,66 @@ | ||
| # Manually triggered workflow for creating a build | ||
| name: Expo Build with given profile | ||
|
|
||
| on: | ||
| workflow_dispatch: | ||
| inputs: | ||
| profile: | ||
| description: "Build profile" | ||
| required: true | ||
| default: "development" | ||
| type: choice | ||
| # Should match the ones in `eas.json` | ||
| options: | ||
| - development | ||
| - development_simulator | ||
| - development_review | ||
| - staging | ||
| - production | ||
| platform: | ||
| description: "Platform" | ||
| required: true | ||
| default: "ios" | ||
| type: choice | ||
| options: | ||
| - android | ||
| - ios | ||
| - all | ||
| clear_cache: | ||
| description: "Clear cache" | ||
| required: true | ||
| default: false | ||
| type: "boolean" | ||
| jobs: | ||
| build: | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: 🏗 Setup repo | ||
| uses: actions/checkout@v4 | ||
|
|
||
| - name: 🏗 Setup Node | ||
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 18.x | ||
| cache: npm | ||
| cache-dependency-path: ./mobile/package-lock.json | ||
|
|
||
| - name: 🏗 Setup Expo and EAS | ||
| uses: expo/expo-github-action@v8 | ||
| with: | ||
| expo-version: latest | ||
| eas-version: latest | ||
| token: ${{ secrets.EXPO_TOKEN }} | ||
|
There was a problem hiding this comment. @lakardion - Cookiecutter is trying to render this and failing to 'bake'. |
||
|
|
||
| - name: 📦 Install dependencies | ||
| working-directory: ./mobile | ||
| run: npm install | ||
|
|
||
| - name: 🚀 Build app | ||
| run: | | ||
| cd mobile | ||
| CLEAR_CACHE_FLAG="" | ||
| if [[ ${{ github.event.inputs.clear_cache }} ]]; then | ||
| CLEAR_CACHE_FLAG="--clear-cache" | ||
| fi | ||
| eas build --profile ${{ github.event.inputs.profile }} --platform ${{ github.event.inputs.platform }} --non-interactive $CLEAR_CACHE_FLAG | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this goes nicely with my open PR as well that creates dynamic review app based builds.
I think dynamically adding them to the eas.json like this allows us to create unique builds. In this case as you have it, each engineer's build will overwrite the others (although at this moment many of us don't really need builds that often).
I also wonder if this can be avoided by removing the channel arg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean initially I wrote this because I happened not to have enough permissions in a project to use the eas cli myself so I just used the action to get a build I needed.
This as you said is not something that we would use often, it is just a convenience, mostly to get development builds that we usually need when we deviate from expo go.