[No QA] Use setup-node and setup-ruby for caching and installs#9815
Conversation
| - uses: actions/setup-node@09ba51f18e18a3756fea1f54d09c6745c064491d | ||
| with: | ||
| node-version: 16 | ||
| cache: npm |
There was a problem hiding this comment.
Note the use of built-in caching as opposed to actions/cache. Since this is maintained by GitHub hopefully it will work better on average than our caching has in the past. Also it's easier / less configuration needed.
| - uses: Expensify/App/.github/actions/composite/setupNode@main | ||
|
|
||
| - uses: actions/setup-ruby@v1 | ||
| - uses: ruby/setup-ruby@08245253a76fa4d1e459b7809579c62bd9eb718a |
There was a problem hiding this comment.
Note the use of https://github.com/ruby/setup-ruby instead of deprecated https://github.com/actions/setup-ruby.
| timeout_minutes: 10 | ||
| max_attempts: 5 | ||
| command: npm ci | ||
| bundler-cache: true |
There was a problem hiding this comment.
This flag runs 'bundle install' and caches installed gems automatically
|
|
||
| - name: Install bundler | ||
| run: | | ||
| bundle config path vendor/bundle |
There was a problem hiding this comment.
From the ruby/setup-ruby docs:
To perform caching, this action will use bundle config --local path $PWD/vendor/bundle.
Therefore, the Bundler path should not be changed in your workflow for the cache to work (no bundle config path).
Since the action already used vendor/bundle for the path, we don't need to worry about setting it before installing bundler.
|
Checks are failing because the
|
Justicea83
left a comment
There was a problem hiding this comment.
Everything looks good if we fix the conflicts
|
It seems we have some linting issues, can we fix it and get it merged ASAP? |
|
Tests are going to fail for the reason described in this comment, so I'm running them locally for good measure: Jest Unit TestsClick to expand!ESLintNOTE: The only failing files here are ones that only exist locally and are not committed to this repo (I have them in my global Validate GitHub ActionsVerify Podfile |
|
@AndrewGable looks like this was merged without passing tests. Please add a note explaining why this was done and remove the |
|
@roryabraham mentioned why here, but these can only be tested on |
|
🚀 Deployed to production by @chiragsalian in version: 1.1.84-13 🚀
|

Details
Fixed Issues
$ n/a
Tests