6fc691beb0
## Introduction In this previous PR https://github.com/twentyhq/twenty/pull/9448 we've refactored the storybook build caching flow to be using the new [actions/cache](https://github.com/actions/cache) `restore` and `save` functions, which significantly improve caching operations duration. In this way, in this PR, we've standardize both of the `restore` and `save` by refactoring the `task-cache` composite action. By creating two new composite actions `save-cache` and `restore-cache` that centralize the paths to cache and the way to compute the primary key. ## Misc - **If no cache** is hit, then a job duration will long for its task duration and nothing else, previously the cache upload would sometimes take up to 3 mins. - **if cache** is hit, then mainly the only time consuming step is the dependencies installation ( which is theory is also cached, in fact twice. We will be having a look on this issue in an upcoming PR )
23 lines
536 B
YAML
23 lines
536 B
YAML
name: Save cache
|
|
inputs:
|
|
key:
|
|
required: true
|
|
description: Primary key to the cache, should be retrieved from `cache-restore` composite action outputs.
|
|
type: string
|
|
additional-paths:
|
|
required: false
|
|
type: string
|
|
|
|
runs:
|
|
using: "composite"
|
|
steps:
|
|
- name: Save cache
|
|
uses: actions/cache/save@v4
|
|
with:
|
|
key: ${{ inputs.key }}
|
|
path: |
|
|
.cache
|
|
.nx/cache
|
|
node_modules/.cache
|
|
packages/*/node_modules/.cache
|
|
${{ inputs.additional-paths }} |