Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 176
    • Issues 176
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Issues
  • #454

Closed
Open
Opened Mar 14, 2025 by Przemyslaw Kaminski@cgenie
  • Report abuse
  • New issue
Report abuse New issue

Add a nix cache and push artifacts from the CI?

This was discussed before, but no issue was created, so I do this.

Basically, we could add a nix cache (e.g. of a free one is attic: https://discourse.nixos.org/t/introducing-attic-a-self-hostable-nix-binary-cache-server/24343). Then the CI would push there and we could benefit by pulling from that cache, instead of building on our machine.

Maybe this is less urgent now, since GHC 9.6.6 is in cache already, it was annoying when we had to build things with flake (as that particular GHC version wasn't in the cache).

Anyways, if we start nix from scratch, it still builds quite a few things (haskell-related).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext#454