I always try to put as little logic into CI-Runner-specific tooling as possible and rather have everything automated via the usual programming language build tooling, which you can run locally.
Yeah I need to start doing this more lol
My employer, garden.io, offers pipelines you can run anywhere: in GitHub Actions, GitLab CI, locally, wherever! We capture all your dependencies in a dependency graph, then cache all your inputs: builds, tests, run scripts. We’re open source at https://github.com/garden-io/garden
act is so hard to use and the docs are terrible. Every time I go to use it I give up a few hours later having gotten nowhere. Incredibly frustrating experience.
Makes me think of dagger.io (why can't techies come up with names outside of a dictionary?)
Because if they try, you get gems like XÆA-12
You do get some pretty good names like Netflix, roomba, Skype, etc.
One of the frustrating things with Dagger is that you still have to set up your pipeline tool. Sure, you’re theoretically running the same thing local and remote, but it doesn’t remove much in the way of CI work. Azure stuff is (was?) less supported. And while the move away from CUE was the right one, there’s still a lot of CUE around.
