The cache key for nix now depends on default.nix and shell.nix in the root folder and all .patch files in the nix folder. Those may change the output of our nix derivations, so must be included. At the same time, there is no reason to include the actions/setup-nix folder. This would only lead to new caches being created every time we update one of the dependent actions in this file. Finally, we never restore caches with a different id any- more. There is no point in having the style job fall back to the static cache for example. The cache keys for cabal can be more explicit: We only have one postgrest.cabal and one relevant cabal.project file. We were missing the cabal.project.freeze file, though, which affects the dependencies used, too.
33 lines
953 B
YAML
33 lines
953 B
YAML
name: Setup Nix
|
|
|
|
description: Installs nix, sets up cachix and installs a subset of tooling.
|
|
|
|
inputs:
|
|
authToken:
|
|
description: Token to pass to cachix
|
|
tools:
|
|
description: Tools to install with nix-env -iA <tools>
|
|
cache-id:
|
|
description: Cache id to use for cache-nix-action
|
|
default: "default"
|
|
|
|
runs:
|
|
using: composite
|
|
steps:
|
|
- uses: nixbuild/nix-quick-install-action@v26
|
|
with:
|
|
nix_version: '2.13.6'
|
|
- name: Restore and cache Nix store
|
|
uses: nix-community/cache-nix-action@v4.0.3
|
|
with:
|
|
key: cache-nix-${{ runner.os }}-${{ inputs.cache }}-${{ hashFiles('**/*.nix', 'nix/**/*.patch') }}
|
|
restore-keys: |
|
|
cache-nix-${{ runner.os }}-${{ inputs.cache }}-
|
|
- uses: cachix/cachix-action@v14
|
|
with:
|
|
name: postgrest
|
|
authToken: ${{ inputs.authToken }}
|
|
- if: ${{ inputs.tools }}
|
|
run: nix-env -f default.nix -iA ${{ inputs.tools }}
|
|
shell: bash
|