TSK-1657: increased stability of test_frontend job

by adding a 'populate cache' step in case compile_frontend does not write the cache
This commit is contained in:
Mustapha Zorgati 2021-06-29 09:19:51 +02:00
parent 1d8dbbf6c3
commit 0879ca596a
No known key found for this signature in database
GPG Key ID: BFF92FDA34CDC6FB
1 changed files with 7 additions and 1 deletions

View File

@ -177,17 +177,23 @@ jobs:
with:
path: web/node_modules
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.
# Theoretically this step below 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
if: steps.web-cache.outputs.cache-hit != 'true'
working-directory: web
run: yarn ci
- name: Cache maven dependencies
id: maven-cache
uses: actions/cache@v2.1.6
with:
path: ~/.m2
key: ${{ runner.os }}-${{ env.CACHE_MAVEN_NAME }}-${{ hashFiles('**/pom.xml') }}
# Theoretically this step below not necessary because we reuse the cache from the 'compile_frontend' job.
# Sometimes the cache is not created, therefore this is a fallback.
- name: Populate cache
run: ./mvnw -B dependency:go-offline -pl :taskana-rest-spring-example-boot -am
if: steps.maven-cache.outputs.cache-hit != 'true'
- name: Download taskana artifacts
uses: actions/download-artifact@v2
with: