95a7b4497e
Summary: We sometimes see workflows fail due to network flakiness, almost always being Windows agents doing a `yarn install`. This change enables storing and reusing Yarn's package cache, and makes `yarn install` more permissive when it does hit the network. https://stackoverflow.com/questions/51508364/yarn-there-appears-to-be-trouble-with-your-network-connection-retrying Pull Request resolved: https://github.com/facebook/yoga/pull/1332 Test Plan: Workflows succeed, and we see cache being restored before yarn install step. Reviewed By: lunaleaps Differential Revision: D48967590 Pulled By: NickGerleman fbshipit-source-id: 55ce6f05496f014512e0153b6646a7ca0ab964d9
24 lines
725 B
YAML
24 lines
725 B
YAML
name: Setup Website envirionment
|
|
|
|
runs:
|
|
using: "composite"
|
|
steps:
|
|
# TODO: Update to latest when website is moved to the workspace version of
|
|
# yoga-layout
|
|
- name: Setup Node environment
|
|
uses: actions/setup-node@v3
|
|
with:
|
|
node-version: 12.x
|
|
cache: yarn
|
|
cache-dependency-path: website/yarn.lock
|
|
env:
|
|
# https://github.com/actions/setup-node/issues/317
|
|
FORCE_COLOR: 0
|
|
|
|
# TODO: the website should be in a yarn workspace with the library, but the
|
|
# current version of gatsby is incompatible with hoisting.
|
|
- name: yarn install
|
|
shell: bash
|
|
run: yarn install --frozen-lockfile --network-timeout 1000000
|
|
working-directory: website
|