GitHub Actions Build Cache

[henrikbjorn]

Is there a way to persist cache between builds on Github Actions and Nixpacks.

I am using GitHub Actions to deploy to fly

My workflow looks like this:

---
name: Deploy

on:
  push:
    branches:
      - main
jobs:
  deploy:
    name: Deploy
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Setup flyctl
        uses: superfly/flyctl-actions/setup-flyctl@master

      - name: Deploy
        run: flyctl deploy --remote-only --nixpacks
        env:
          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}

[henrikbjorn]

Might not be that relevant for Fly since they are using a remote worker to build etc.

However it is relevant for the case where Nixpacks is used to build and image and then push it to a docker registry

[ebg1223]

have this same question! Different use case, where we are building an image and pushing directly to registry. Would like to know where the cache is stored so that it can be persisted.

[iloveitaly]

@coffee-cup running into the same Q here: where is the cache stored and how can i persist it across GHA runs