Welcome to the Functional Programming Zulip Chat Archive. You can join the chat here.
Guys, what do you think about considering Github Actions instead of Travis? It's one less service to keep track of and Actions seem to be nicely integrated.
(I'm a GitLab guy, but I guess that's for another debate)
Actions is pretty nice. I use it with Nix on my projects. Minimal configuration: https://github.com/srid/rib/blob/master/.github/workflows/ci.yaml
@Love Waern (King of the Homeless) @Georgi Lyubenov // googleson78 :up:
I don't know enough about Travis or Github Actions to tell which one is better. I'll defer to you guys on this one. If you think it's better, then we'll go with it.
An advantage of Github Action is that disparate actions can be composed. So you have cachix action taking care of nix cache, and a custom action that does nix-build and then may be another deploy action that does the deployment of built assets.
Hmm, I was playing with GitLab CI and it seems to be pretty good - if we wouldn't mind switching hosting service, we could get the highest plan for free as an open source project: https://about.gitlab.com/solutions/open-source/program/
Old thread but for the record, having used many many CI services, I can definitely say GitHub Actions is really high up there in terms of usability, and I personally preferred it to GitLab CI (also generally has shorter wait times to start a build IME)
have you encountered any issues with the 5gb cache limit? seems like something you would hit really quickly with a haskell project