Github action to use an Attic binary cache https://cachix.org
  • TypeScript 67.8%
  • Nix 26.9%
  • JavaScript 5.3%
Find a file
2020-04-10 13:12:59 +02:00
.github/workflows bump github actions 2020-03-14 11:56:25 +01:00
__tests__ saneSplit -> nonEmptySplit 2019-10-03 13:26:42 +02:00
lib A tiny bit more consistent logging 2020-03-14 11:49:51 +01:00
src A tiny bit more consistent logging 2020-03-14 11:49:51 +01:00
.gitignore Initial commit 2019-09-30 15:32:36 +02:00
action.yml Add nixBuildArgs parameter 2020-02-27 16:46:25 +01:00
jest.config.js Initial commit 2019-09-30 15:32:36 +02:00
LICENSE Split Nix installation into separate action 2019-10-02 16:25:24 +02:00
package.json Split Nix installation into separate action 2019-10-02 16:25:24 +02:00
README.md README: bump actions 2020-03-14 12:02:12 +01:00
test-with-arg.nix Add nixBuildArgs parameter 2020-02-27 16:46:25 +01:00
test.nix fix for #3 2019-10-03 15:43:16 +02:00
tsconfig.json Initial commit 2019-09-30 15:32:36 +02:00
yarn.lock Bump acorn from 5.7.3 to 5.7.4 2020-04-05 05:48:37 +00:00

cachix-action

github actions badge

Build software only once using Nix with the help of Cachix.

This action will configure Cachix and invoke nix-build.

Why do I need this

Because you'd like for your CI to be fast. Let me explain.

Directory-based caching on a typical CI doesn't work well for Nix.

/nix/store is a global storage of everything Nix operates on. These are your sources, patches, tarballs, packages, configuration.

A directory-based cache requires downloading a whole store, including the irrelevant parts. cachix-action will only fetch what's needed by configuring a Nix binary cache.

When the build is done, cachix-action only has to upload the new store paths, rather than syncing the whole store.

Purging paths from a directory-based cache is not feasible because it'd have to be aware of all branches and their respective contents somehow.

Usage

1. Login to Cachix and create a new cache.

1. Follow getting started to create your signing key
2. Backup the signing key in the process.

2. As an admin of your github repository:

1. Click on Settings
2. Click on Secrets ([If missing, you need to sign up first for actions beta](https://github.com/features/actions))
3. Add your signing key value under name `CACHIX_SIGNING_KEY`.

3. Create .github/workflows/test.yml in your repo with the following contents:

name: "Test"
on:
  pull_request:
  push:
jobs:
  tests:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - uses: cachix/install-nix-action@v8
    - uses: cachix/cachix-action@v5
      with:
        name: mycache
        signingKey: '${{ secrets.CACHIX_SIGNING_KEY }}'
        # Only needed for private caches
        authToken: '${{ secrets.CACHIX_AUTH_TOKEN }}'

Alternatively, you can use this action to only configure cachix for substitution:

...
    - uses: cachix/cachix-action@v5
      with:
        name: mycache
        skipNixBuild: true
        # Only needed for private caches
        authToken: '${{ secrets.CACHIX_AUTH_TOKEN }}'
...

See action.yml for all options.


Hacking

Install the dependencies

$ yarn install

Build the typescript

$ yarn build

Run the tests ✔️

$ yarn test