TSK-1657: fixed path to yarn.lock files so that cache gets computed correctly
This commit is contained in:
parent
75f52f04d8
commit
1d8dbbf6c3
|
@ -92,7 +92,7 @@ jobs:
|
|||
uses: actions/cache@v2.1.6
|
||||
with:
|
||||
path: web/node_modules
|
||||
key: ${{ runner.OS }}-${{ env.CACHE_WEB_NAME }}-${{ hashFiles('**/yarn-lock.json') }}
|
||||
key: ${{ runner.OS }}-${{ env.CACHE_WEB_NAME }}-${{ hashFiles('**/yarn.lock') }}
|
||||
- name: Cache maven dependencies (for web)
|
||||
uses: actions/cache@v2.1.6
|
||||
with:
|
||||
|
@ -176,7 +176,7 @@ jobs:
|
|||
uses: actions/cache@v2.1.6
|
||||
with:
|
||||
path: web/node_modules
|
||||
key: ${{ runner.OS }}-${{ env.CACHE_WEB_NAME }}-${{ hashFiles('**/yarn-lock.json') }}
|
||||
key: ${{ runner.OS }}-${{ env.CACHE_WEB_NAME }}-${{ hashFiles('**/yarn.lock') }}
|
||||
# Theoretically this is not necessary because we reuse the cache from the 'compile_frontend' job.
|
||||
# Sometimes the cache is not created, therefore this is a fallback.
|
||||
- name: Install Dependencies
|
||||
|
|
Loading…
Reference in New Issue