Should the key and restore-keys be unique per Job?

[distante]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Cache

Discussion Details

I am a little but lost about the cache keys. We use nx (no cloud) and we want save and restore the .nx/cache folder.

Currently all the jobs have this step

      - name: Restore nx cache
        id: nxcache
        uses: actions/cache@v4
        with:
          path: .nx/cache
          key: ${{ runner.os }}-nxcache-${{ hashFiles('package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-nxcache-

I am first taking the code to refactor and I am wondering if that key is wrong and it should at least contain the name of the job.

I have seen a couple of times a log like "the cache can not be set because other job is writing it". That is why I started wondering.

Any help is appreciated!

Thanks!

[Eh-Vee]

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows

You can find more precise answers through the link, but from my understanding the restoration key is unique every time.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬