You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just for reference, today downstream users should already be able to use tools from fuel.nix in CI actions with something like this:
jobs:
my-build-job:
runs-on: ubuntu-lateststeps:
- uses: actions/[email protected]
- uses: cachix/install-nix-action@v20with:
nix_path: nixpkgs=channel:nixos-unstableextra_nix_config: | extra-substituters = https://fuellabs.cachix.org extra-trusted-public-keys = fuellabs.cachix.org-1:3gOmll82VDbT7EggylzOVJ6dr0jgPVU/KMN6+Kf8qx8=
- run: nix shell github:fuellabs/fuel.nix#forc-0-39-0# Following steps now have `forc` version `0.39.0` available.
- run: forc build
But yes, it would be great to test latency, and perhaps provide some wrapper action that takes care of the cachix installation with the necessary binary cache etc.
If it turns out that relying directly on the fuellabs cache does take too long, I'd imagine there's some way to provide a docker image that provides forc pre-fetched? I don't have enough docker experience to be sure 😅
This would give us an idea of whether
fuel.nix
could be a viable replacement forfuelup
in CI, in terms of latency to install forc.The text was updated successfully, but these errors were encountered: